[JIRA] (JENKINS-36609) Indicate 'current' and 'old' stages in the aggregated view
Title: Message Title howama created an issue Jenkins / JENKINS-36609 Indicate 'current' and 'old' stages in the aggregated view Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Jul/12 8:44 AM Priority: Minor Reporter: howama Would it be possible to add a CSS class to stages to indicate if they are or are not the latest view in the aggregated views? At the moment there is no differentiation, so an aggregated view can appear all green, when one job part way through is in the build queue, or a single job in the middle has failed. It would be better if we could add some visual indication to the later builds to show that they are from an older instance of the pipeline. The version number does help for this, but is difficult to see from a full screen radiator view. Add Comment
[JIRA] (JENKINS-36608) Indicate previous status for building jobs in aggregator view
Title: Message Title howama created an issue Jenkins / JENKINS-36608 Indicate previous status for building jobs in aggregator view Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Jul/12 8:42 AM Priority: Minor Reporter: howama Would it be possible to add a css class to jobs in the aggregator view to indicate the previous status of the job, when it is currently building. At the moment, when we start a stage, large sections of the radiator go to black with the blue progress bar. It would be good if this predominantly remained its previous colour (e.g. red/green), with the progress bar as an overlay. This would help give more indication of the current status and which builds to watch in particular. The wall display plugin has the same effect - see the first screenshot in https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=57184000 Progress bars are shown as overlays with the main colour taken from the previous build. Add Comment
[JIRA] (JENKINS-36606) Indicate queued jobs in aggregated view
Title: Message Title howama created an issue Jenkins / JENKINS-36606 Indicate queued jobs in aggregated view Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Jul/12 8:32 AM Priority: Minor Reporter: howama Please could you add a new css class to any jobs which are currently in the build queue, particularly in the aggregator view? This will help to check if a build is really currently green, or may be waiting for resources to build a new change. The wall display plugin has this behaviour, with CSS showing yellow dots on the dashboard when items are queued. (the number of dots representing the position in the queue). Example images can be seen in: https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=57184000 Add Comment
[JIRA] (JENKINS-36181) Support folder plugin
Title: Message Title howama created an issue Jenkins / JENKINS-36181 Support folder plugin Issue Type: Improvement Assignee: magnayn Components: maven-repository-plugin Created: 2016/Jun/23 9:42 AM Priority: Minor Reporter: howama The repository plugin currently exposes a repository for jobs contained in folders of the form: http://jenkins/job/1s/job/<>/job/<>//maven-repository/repositoryChain/ Downstream projects currently trying to use this are directed to an invalid url for the job which does not include the folder. It doesn't appear to be possible to add the folder to the plugin/repository version of the URL: http://jenkins/plugin/repository/project/<>/Build/5/repositoryChain Add Comment
[JIRA] [git] (JENKINS-4111) Can't use parameters in git plugin "Branches to build" configuration
howama commented on JENKINS-4111 Can't use parameters in git plugin "Branches to build" configuration Not sure if this is a different issue, but we're having problems with git polling when parameters are used in the branch field - a single (random?) branch is being built continuously rather than just the branch that has changed. We'd like to create a parameterised build with the branch as the build parameter, defaulting to :^(?!.master).$ i.e. we want automatic builds of all commits to any non-master branches and also to have the option to build a specific branch manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release] (JENKINS-5079) Release plugin is not available for multi-config projects
howama commented on JENKINS-5079 Release plugin is not available for multi-config projects Not sure if this is a different use case, but at least for us using maven we need the release to be performed on only one of the configurations in a multi-config project. We use multi-config to run the tests in different environments (usually webdriver browsers), but only want to create a single release. The current approach would result in duplicate SCM tags, updates to poms, deployments of released versions to nexus, etc (if we didn't have tools in place to stop them) Could an option be added to select a single config matrix to be used for release builds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-9943) Support releases on Matrix/Multi-Config Bulids
howama commented on JENKINS-9943 Support releases on Matrix/Multi-Config Bulids Would it be possible to run the release on a single configuration (either nominated at release time or in config). Our current use case is that we would like to use the matrix builds to run webdriver based tests on multiple browsers, but still want to make releases via jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-19747) Claim information not shown while re-building
howama resolved JENKINS-19747 as Fixed Claim information not shown while re-building Now shown if the job is re-building and last completed job was claimed. Change By: howama (19/Nov/13 9:03 AM) Status: Open Resolved Assignee: Christian Pelster howama Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-17141) Integration with Claim plugin
howama resolved JENKINS-17141 as Fixed Integration with Claim plugin The job info view (click on a job to see it) now includes the claim user and reason string. Change By: howama (19/Nov/13 9:02 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20552) Show system messages
howama resolved JENKINS-20552 as Fixed Show system messages Change By: howama (19/Nov/13 9:00 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16180) Make paintInterval configurable via URL
howama resolved JENKINS-16180 as Fixed Make paintInterval configurable via URL See previous commit comment. Also works via the &jenkinsPaintInterval= query parameter Change By: howama (18/Nov/13 9:47 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-15805) Wall Display shows "loading jobs..." forever
howama resolved JENKINS-15805 as Fixed Wall Display shows "loading jobs..." forever Just tried and the plugin does now give an error rather than just loading jobs if the url is incorrect. Change By: howama (18/Nov/13 9:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16857) Doesn't list all builds
howama commented on JENKINS-16857 Doesn't list all builds This always works fine for me - the wall display shows the same as the list views. Can anyone else confirm this bug or add more details? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16370) Deleting oldest build, deletes the build but not removes the link and results in 404 error
howama resolved JENKINS-16370 as Incomplete Deleting oldest build, deletes the build but not removes the link and results in 404 error The wall display plugin doesn't include any functionality to delete a build. Please could you give more details of the location of links that you clicked on to delete the build and then to view the build Change By: howama (18/Nov/13 9:46 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16657) Wall Display JS Error: Cannot read property 'claimed' of null
howama resolved JENKINS-16657 as Fixed Wall Display JS Error: Cannot read property 'claimed' of null Change By: howama (18/Nov/13 9:44 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-18987) View crashes when last known failure does not exist
howama commented on JENKINS-18987 View crashes when last known failure does not exist Do you have the _javascript_ error for this or results of the json api call? This sounds like an error with core jenkins rather than the plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-13556) Unprintable character in executor name in JSON API output
howama resolved JENKINS-13556 as Duplicate Unprintable character in executor name in JSON API output Seem to be a duplicate of JENKINS-13865, which is fixed Change By: howama (18/Nov/13 9:41 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20551) Claim border moves text out of line
howama resolved JENKINS-20551 as Fixed Claim border moves text out of line Change By: howama (18/Nov/13 9:19 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20551) Claim border moves text out of line
howama updated JENKINS-20551 Claim border moves text out of line Attached output from howama:master fork which fixes the text alignment by using a background Change By: howama (18/Nov/13 11:45 AM) Attachment: jenkins.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20551) Claim border moves text out of line
howama created JENKINS-20551 Claim border moves text out of line Issue Type: Bug Assignee: howama Attachments: claimborder.png Components: jenkinswalldisplay, walldisplay Created: 13/Nov/13 9:12 AM Description: See attached image. When builds are claimed, the build text is too low in the section for that build, sometimes overlapping the claim information. I will experiment with ideas for fixing this - currently working on using a background pattern to identify claims rather than a border, which would remove most of the pixel based calculations. Project: Jenkins Priority: Minor Reporter: howama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-19770) Load initial configuration straight away
howama resolved JENKINS-19770 as Fixed Load initial configuration straight away Thanks for merging - loads much faster now. Change By: howama (13/Nov/13 9:07 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20552) Show system messages
howama created JENKINS-20552 Show system messages Issue Type: Improvement Assignee: Unassigned Components: jenkinswalldisplay, walldisplay Created: 13/Nov/13 9:13 AM Description: Please could system messages be shown on the radiator, particularly the "Jenkins is going to shut down" message Project: Jenkins Priority: Major Reporter: howama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15302) Restrict to last change date
howama resolved JENKINS-15302 as Not A Defect Restrict to last change date I was thinking of an extension of the builds to display selection to include "modified this week", which would work like "active this week", but ignore stable builds that were triggered by timer or upstream jobs. However, I've just discovered that recent versions of jenkins allow very flexible filtering of views, so this can already be achieved in jenkins with a little more configuration of the view. I'm using the following filters: "At least one build was" "Triggerd by User", 3.0 days "At least one build was" "Triggerd by SCM Poll", 3.0 days "At least one build was" "Triggerd by Remote", 3.0 days "At least one build was" "Triggerd by CLI", 3.0 days "At least one build was" "Not Stable", 3.0 days "Build Status", "Currently Building", "In Build Queue" Change By: howama (25/Sep/12 2:08 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15302) Restrict to last change date
howama created JENKINS-15302 Restrict to last change date Issue Type: Improvement Assignee: Christian Pelster Components: walldisplay Created: 25/Sep/12 1:43 PM Description: Firstly, thanks for the excellent wall display plugin. Would it be possible to extend the restrictions of job to show to be based on the job's changelog in addition to build times? Most of our builds have nightly runs, to check that the infrastructure is running ok, but we're only really interested in jobs that either we're actively working on (committing changes), or that are unstable for other reasons. Project: Jenkins Priority: Minor Reporter: howama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14671) Use JIRA Remote application links instead of comments
howama created JENKINS-14671 Use JIRA Remote application links instead of comments Issue Type: New Feature Assignee: Unassigned Components: jira Created: 02/Aug/12 6:03 PM Description: Many people have requested that this plugin doesn't spam the jira comments section (e.g. JENKINS-12605). JIRA plugins such as marvalution may work for in-house jira instances, but not hosted or on-demand instances. Instead of using comments, could the new jira remote issue links be created instead. These will be shown separately from the comments and could link directly to the jenkins builds. https://developer.atlassian.com/display/JIRADEV/Fields+in+Remote+Issue+Links Project: Jenkins Priority: Major Reporter: howama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12390) Jira plugin cannot be configured to connect to Atlassian on demand instances
howama commented on JENKINS-12390 Jira plugin cannot be configured to connect to Atlassian on demand instances The plugin does work with onDeman, just gives a warning in the configuration screen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
