[JIRA] (JENKINS-34793) Request for rebuild last column
Title: Message Title Fred G updated an issue Jenkins / JENKINS-34793 Request for rebuild last column Change By: Fred G Summary: Extra-columns plug-in: Request for Rebuild Last rebuild last column Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34793) Extra-columns plug-in: Request for Rebuild Last
Title: Message Title Fred G updated an issue Jenkins / JENKINS-34793 Extra-columns plug-in: Request for Rebuild Last Change By: Fred G Component/s: rebuild-plugin Component/s: extra-columns-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34793) Request for rebuild last column
Title: Message Title Fred G commented on JENKINS-34793 Re: Request for rebuild last column Sorry for the late reply. I'd like to keep the extra-columns plug-in free from dependencies to other plug-ins as much as possible. That's why I'd recommend to include this column in the rebuild plugin instead. I will reassign this ticket to the right component and adjust the title. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34793) Request for rebuild last column
Title: Message Title Fred G assigned an issue to ragesh_nair Jenkins / JENKINS-34793 Request for rebuild last column Change By: Fred G Assignee: Fred G ragesh_nair Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36632) Pipeline support
Title: Message Title Fred G commented on JENKINS-36632 Re: Pipeline support Sorry Mark Hudson this issue is related to the enable/disabled project column, not the job-type column. AFAICT pipeline jobs can not (yet?) be disabled/enabled. Jesse Glick: please correct me if I'm wrong! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G commented on JENKINS-40477 Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Jesse Glick Is there a reliable way to find out the last build node of a workflow/pipeline job? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36632) Pipeline support
Title: Message Title Fred G commented on JENKINS-36632 Re: Pipeline support Thanks for the feedback Jesse. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G commented on JENKINS-40477 Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Thanks Jesse for the feedback. I will fix the ClassCastException, but since I currently don't see a nice way to show (potentially) more than one build node in a column, I won't implement this. If someone has an idea how this can be done in a reasonable way, I'm looking forward to their pull request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G closed an issue as Won't Fix Jenkins / JENKINS-40477 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Change By: Fred G Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G updated JENKINS-40477 Jenkins / JENKINS-40477 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Change By: Fred G Status: In Review Closed Resolution: Won't Fix Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G updated JENKINS-40477 Jenkins / JENKINS-40477 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Change By: Fred G Status: Closed In Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Fred G commented on JENKINS-40477 Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild I've set it to "Won't Fix" because I do not plan to implement support for pipeline jobs in the LastBuildNode column. But you are right... I did fix the CCE, so "Fixed" is the better resolution. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-12728) new column: "Last successful artifacts"?
Title: Message Title Fred G commented on JENKINS-12728 Re: new column: "Last successful artifacts"? Hi Viktor, I understand that it would be nice to have faster access to build artifacts, but I'm not sure how this should be implemented. When every job has only one build artifact (e.g. a Zip file), a column with a simple link to that file is good enough. But what happens when there are many build artifacts, let's say 5 Zip files and a log file. Should they all be shown in the column individually, which will make the column quite big? Or as you suggested a link to a zip that contains all artifacts? Zipping everything together might be a problem if you only want specific (small) build artifacts and don't care about the rest (big files). Regards, Fred Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-12728) new column: "Last successful artifacts"?
Title: Message Title Fred G assigned an issue to Viktor Buchkivskyi Jenkins / JENKINS-12728 new column: "Last successful artifacts"? Change By: Fred G Assignee: adam wolf Viktor Buchkivskyi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33867) Wrong link to console output when using folders and view in current url
Title: Message Title Fred G commented on JENKINS-33867 Re: Wrong link to console output when using folders and view in current url I can't reproduce this problem with Jenkins 2.32.2 and Extra-Columns Plugin 1.17. Are you sure, that you are referring to the "Last build console column" of the Extra-Columns Plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33867) Wrong link to console output when using folders and view in current url
Title: Message Title Fred G closed an issue as Cannot Reproduce Jenkins / JENKINS-33867 Wrong link to console output when using folders and view in current url Change By: Fred G Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [collapsing-console-sections-plugin] (JENKINS-34757) NPE while trying to access console in Jenkins 2.0 / 2.3
Title: Message Title Fred G updated an issue Jenkins / JENKINS-34757 NPE while trying to access console in Jenkins 2.0 / 2.3 Caused by: java.lang.NullPointerException at org.jvnet.hudson.plugins.collapsingconsolesections.CollapsingSectionsConfiguration.getSectionDefinitions(CollapsingSectionsConfiguration.java:56) at org.jvnet.hudson.plugins.collapsingconsolesections.CollapsingSectionNote$DescriptorImpl.getSectionDefinitions(CollapsingSectionNote.java:103) at org.jvnet.hudson.plugins.collapsingconsolesections.CollapsingSectionAnnotatorFactory.newInstance(CollapsingSectionAnnotatorFactory.java:40) Looks like collapsing-console-sections-plugin is actually causing the NPE. Change By: Fred G Component/s: collapsing-console-sections-plugin Component/s: console-column-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [collapsing-console-sections-plugin] (JENKINS-34757) NPE while trying to access console in Jenkins 2.0 / 2.3
Title: Message Title Fred G assigned an issue to Dean Yu Jenkins / JENKINS-34757 NPE while trying to access console in Jenkins 2.0 / 2.3 Change By: Fred G Assignee: Fred G Dean Yu Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [collapsing-console-sections-plugin] (JENKINS-34757) NPE while trying to access console in Jenkins 2.0 / 2.3
Title: Message Title Fred G commented on JENKINS-34757 Re: NPE while trying to access console in Jenkins 2.0 / 2.3 Probably a duplicate of JENKINS-30690 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G updated an issue Jenkins / JENKINS-26345 "CVS Symbolic Name parameter" not working any more Change By: Fred G Component/s: cvs-plugin Component/s: cvs-tag-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G commented on JENKINS-26345 Re: "CVS Symbolic Name parameter" not working any more Added a potential fix in this pull request: https://github.com/jenkinsci/cvs-plugin/pull/43 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G assigned an issue to Michael Clarke Jenkins / JENKINS-26345 "CVS Symbolic Name parameter" not working any more Change By: Fred G Assignee: Michael Clarke Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G updated an issue Jenkins / JENKINS-26345 "CVS Symbolic Name parameter" not working any more Change By: Fred G Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [console-column-plugin] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Title: Message Title Fred G assigned an issue to Fred G Jenkins / JENKINS-20724 MultiJob project console output link is broken if job is opened from a view Change By: Fred G Assignee: Fred G Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [console-column-plugin] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Title: Message Title Fred G commented on JENKINS-20724 Re: MultiJob project console output link is broken if job is opened from a view Should be fixed, once https://github.com/jenkinsci/console-column-plugin/pull/2 has been merged. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extra-columns-plugin] (JENKINS-21295) Project Description column configs for trim and width not correctly redisplaying
Title: Message Title Fred G closed an issue as Fixed Please re-open if necessary. Jenkins / JENKINS-21295 Project Description column configs for trim and width not correctly redisplaying Change By: Fred G Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extra-columns-plugin] (JENKINS-21366) Add Columns to show, Display Name, Project Name, Workspace
Title: Message Title Fred G closed an issue as Incomplete Requested information is still missing, so I guess it's not that important. Jenkins / JENKINS-21366 Add Columns to show, Display Name, Project Name, Workspace Change By: Fred G Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G assigned an issue to Fred G Jenkins / JENKINS-21870 'Build-Node-Column: Performance decreases when number of slaves increase Change By: Fred G Assignee: Fred G Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G updated an issue Jenkins / JENKINS-21870 'Build-Node-Column: Performance decreases when number of slaves increase Change By: Fred G Component/s: extra-columns-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G assigned an issue to Kurt Jenkins / JENKINS-21870 'Build-Node-Column: Performance decreases when number of slaves increase Change By: Fred G Assignee: Fred G Kurt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G commented on JENKINS-21870 Re: 'Build-Node-Column: Performance decreases when number of slaves increase I've migrated the last build node column to the Extra Columns Plugin (version 1.16+) and added a potential fix for this issue. Please test and report back if you still see a performance issue with the new column. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G started work on JENKINS-21870 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G commented on JENKINS-21870 Re: 'Build-Node-Column: Performance decreases when number of slaves increase Thanks for the feedback. Glad to hear that the issue is fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-node-column-plugin] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
Title: Message Title Fred G closed an issue as Fixed Jenkins / JENKINS-21870 'Build-Node-Column: Performance decreases when number of slaves increase Change By: Fred G Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extra-columns-plugin] (JENKINS-32871) add environment variable view
Title: Message Title Fred G commented on JENKINS-32871 Re: add environment variable view So you are requesting a new column that shows one or more environment variables, correct? Please provide a use case why you need this kind of column. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extra-columns-plugin] (JENKINS-32871) add environment variable view
Title: Message Title Fred G assigned an issue to mor lajb Jenkins / JENKINS-32871 add environment variable view Change By: Fred G Assignee: Fred G mor lajb Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] (JENKINS-12598) In 2.0 update you need to specify branch for every module
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161343#comment-161343 ] Fred G commented on JENKINS-12598: -- I agree, my mockup is definitely not the best. Nevertheless I think there is a need for a text field that allows a large number of modules to be pasted in. That's also what Ulli requested in the issue's description. As mentioned on IRC, when a large number of modules is checked out, it's pretty save to assume that no custom local names are used. Therefore no local name field is needed in that case. If a user wants to use local names anyways he can still specify them as single modules. > In 2.0 update you need to specify branch for every module > - > > Key: JENKINS-12598 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12598 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Reporter: Ulli Hafner >Priority: Critical > Attachments: Jenkins_CvsPluginModules.png, > repositoryLocationProposal.png > > > After an upgrade to the new 2.0 version of the cvs plug-in we now need to > specify the "Module location" (trunk, branch) for each module. This is quite > cumbersome if you have a lot of modules. In the 1.x plug-in releases you are > able to select a given branch for all modules in one text field. > While I think the new "feature" has a lot of use cases (i.e., having trunk > and branches mixed), the usability could be improved here. My requirement is > to select/change the branch (or trunk) for all modules in a simple way. > A non-Ajax suggestion would be to have a "default" entry in the Selection, > i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at > the top of the cvs configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13387 started by Fred G. > Convert "Delete this build" buttons into links in the sidepanel > --- > > Key: JENKINS-13387 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G > Labels: gui > Attachments: DeleteBuildButtons_MatrixBuild.png, > DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, > DeleteBuildLinks_MatrixConfig.png > > > The "Delete this build" buttons on build pages and also the "Delete this > build and all configurations of this build" buttons on matrix build pages > should be converted to links in the sidepanel of the respective pages (see > Screenshots). > This simplifies the user experience of deleting an object (see the "Delete > Project" link in the sidepanel of project pages). > Having the links in the sidepanel also makes them accessible through the > newly added context menus that came with the breadcrumbs. > Recent discussion about this topic: > https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
Fred G created JENKINS-13387: Summary: Convert "Delete this build" buttons into links in the sidepanel Key: JENKINS-13387 URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Assignee: Fred G Attachments: DeleteBuildButtons_MatrixBuild.png, DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, DeleteBuildLinks_MatrixConfig.png The "Delete this build" buttons on build pages and also the "Delete this build and all configurations of this build" buttons on matrix build pages should be converted to links in the sidepanel of the respective pages (see Screenshots). This simplifies the user experience of deleting an object (see the "Delete Project" link in the sidepanel of project pages). Having the links in the sidepanel also makes them accessible through the newly added context menus that came with the breadcrumbs. Recent discussion about this topic: https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert "Delete this build" buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161401#comment-161401 ] Fred G commented on JENKINS-13387: -- Pull request: https://github.com/jenkinsci/jenkins/pull/431 > Convert "Delete this build" buttons into links in the sidepanel > --- > > Key: JENKINS-13387 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G > Labels: gui > Attachments: DeleteBuildButtons_MatrixBuild.png, > DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, > DeleteBuildLinks_MatrixConfig.png > > > The "Delete this build" buttons on build pages and also the "Delete this > build and all configurations of this build" buttons on matrix build pages > should be converted to links in the sidepanel of the respective pages (see > Screenshots). > This simplifies the user experience of deleting an object (see the "Delete > Project" link in the sidepanel of project pages). > Having the links in the sidepanel also makes them accessible through the > newly added context menus that came with the breadcrumbs. > Recent discussion about this topic: > https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G updated JENKINS-13389: - Description: To clean up the Jenkins UI, all "actions" should be links in the sidepanel menu on the left side of the screen. The "View as plain text" link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the console output page is shown (similiar to the "Wipe out workspace"-link which only appears when the workspace is selected). was: To clean up the Jenkins UI, all "actions" should be links in the sidepanel menu on the right side of the screen. In this case, the "View as plain text" link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the Console Output page is shown (similiar to the "Wipe out workspace"-link which only appears when the workspace is selected). > Move "View as plain text" link on console output page from top right to the > sidepanel. > -- > > Key: JENKINS-13389 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Priority: Minor > Labels: gui > Attachments: ViewAsPlainText_Link.png > > > To clean up the Jenkins UI, all "actions" should be links in the sidepanel > menu on the left side of the screen. > The "View as plain text" link that appears on the top right corner of the > console output page should be > moved to the sidepanel (see screenshot). > The link should only appear when the console output page is shown (similiar > to the "Wipe out workspace"-link > which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
Fred G created JENKINS-13389: Summary: Move "View as plain text" link on console output page from top right to the sidepanel. Key: JENKINS-13389 URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Priority: Minor Attachments: ViewAsPlainText_Link.png To clean up the Jenkins UI, all "actions" should be links in the sidepanel menu on the right side of the screen. In this case, the "View as plain text" link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the Console Output page is shown (similiar to the "Wipe out workspace"-link which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13389 started by Fred G. > Move "View as plain text" link on console output page from top right to the > sidepanel. > -- > > Key: JENKINS-13389 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G >Priority: Minor > Labels: gui > Attachments: ViewAsPlainText_Link.png > > > To clean up the Jenkins UI, all "actions" should be links in the sidepanel > menu on the left side of the screen. > The "View as plain text" link that appears on the top right corner of the > console output page should be > moved to the sidepanel (see screenshot). > The link should only appear when the console output page is shown (similiar > to the "Wipe out workspace"-link > which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reassigned JENKINS-13389: Assignee: Fred G > Move "View as plain text" link on console output page from top right to the > sidepanel. > -- > > Key: JENKINS-13389 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G >Priority: Minor > Labels: gui > Attachments: ViewAsPlainText_Link.png > > > To clean up the Jenkins UI, all "actions" should be links in the sidepanel > menu on the left side of the screen. > The "View as plain text" link that appears on the top right corner of the > console output page should be > moved to the sidepanel (see screenshot). > The link should only appear when the console output page is shown (similiar > to the "Wipe out workspace"-link > which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move "View as plain text" link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161402#comment-161402 ] Fred G commented on JENKINS-13389: -- Pull request: https://github.com/jenkinsci/jenkins/pull/432 > Move "View as plain text" link on console output page from top right to the > sidepanel. > -- > > Key: JENKINS-13389 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Fred G >Assignee: Fred G >Priority: Minor > Labels: gui > Attachments: ViewAsPlainText_Link.png > > > To clean up the Jenkins UI, all "actions" should be links in the sidepanel > menu on the left side of the screen. > The "View as plain text" link that appears on the top right corner of the > console output page should be > moved to the sidepanel (see screenshot). > The link should only appear when the console output page is shown (similiar > to the "Wipe out workspace"-link > which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5779) Config link/button per job on main home page
[ https://issues.jenkins-ci.org/browse/JENKINS-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161550#comment-161550 ] Fred G commented on JENKINS-5779: - The [Extra Columns Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Extra+Columns+Plugin] lets you add a column with a config button for every job. > Config link/button per job on main home page > > > Key: JENKINS-5779 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5779 > Project: Jenkins > Issue Type: New Feature > Components: gui > Environment: Currently using: Hudson ver. 1.327 >Reporter: jlorenzen >Priority: Trivial > > It'd be very useful if there was a config link/button on the home page per > job. I'm constantly needing to view/change the config goals for our jobs. > Also for readonly users it'd be nice if they could view the maven goals for > example that are running for a job. Maybe have some type of readonly view of > the config page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5779) Config link/button per job on main home page
[ https://issues.jenkins-ci.org/browse/JENKINS-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-5779. - Assignee: Fred G Resolution: Fixed All requested features have been implemented. > Config link/button per job on main home page > > > Key: JENKINS-5779 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5779 > Project: Jenkins > Issue Type: New Feature > Components: gui > Environment: Currently using: Hudson ver. 1.327 >Reporter: jlorenzen >Assignee: Fred G >Priority: Trivial > > It'd be very useful if there was a config link/button on the home page per > job. I'm constantly needing to view/change the config goals for our jobs. > Also for readonly users it'd be nice if they could view the maven goals for > example that are running for a job. Maybe have some type of readonly view of > the config page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5779) Config link/button per job on main home page
[ https://issues.jenkins-ci.org/browse/JENKINS-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reassigned JENKINS-5779: --- Assignee: jlorenzen (was: Fred G) Please close this issue or re-open if necessary. > Config link/button per job on main home page > > > Key: JENKINS-5779 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5779 > Project: Jenkins > Issue Type: New Feature > Components: gui > Environment: Currently using: Hudson ver. 1.327 >Reporter: jlorenzen >Assignee: jlorenzen >Priority: Trivial > > It'd be very useful if there was a config link/button on the home page per > job. I'm constantly needing to view/change the config goals for our jobs. > Also for readonly users it'd be nice if they could view the maven goals for > example that are running for a job. Maybe have some type of readonly view of > the config page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1181) Disabling a Job from the main page
[ https://issues.jenkins-ci.org/browse/JENKINS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Disabling a Job from the main page > -- > > Key: JENKINS-1181 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1181 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: Dieter De Meyer > > It would be easier to disable a specific Job from the main page that lists all > the available jobs (cfr. link for 'Schedule A Build'), > instead of going to the job and clicking configure and disabling it with the > checkbox and finally saving the configuration. > Or on a separate page that lists the jobs so you can select multiple jobs to > disable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1181) Disabling a Job from the main page
[ https://issues.jenkins-ci.org/browse/JENKINS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161553#comment-161553 ] Fred G commented on JENKINS-1181: - The [Extra Columns Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Extra+Columns+Plugin] lets you choose a column that adds a disable/enable button for every job. I think it's pretty close to "batch disabling", maybe not perfect but quite fast. > Disabling a Job from the main page > -- > > Key: JENKINS-1181 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1181 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: Dieter De Meyer > > It would be easier to disable a specific Job from the main page that lists all > the available jobs (cfr. link for 'Schedule A Build'), > instead of going to the job and clicking configure and disabling it with the > checkbox and finally saving the configuration. > Or on a separate page that lists the jobs so you can select multiple jobs to > disable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1181) Disabling a Job from the main page
[ https://issues.jenkins-ci.org/browse/JENKINS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reassigned JENKINS-1181: --- Assignee: Fred G > Disabling a Job from the main page > -- > > Key: JENKINS-1181 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1181 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: Dieter De Meyer >Assignee: Fred G > > It would be easier to disable a specific Job from the main page that lists all > the available jobs (cfr. link for 'Schedule A Build'), > instead of going to the job and clicking configure and disabling it with the > checkbox and finally saving the configuration. > Or on a separate page that lists the jobs so you can select multiple jobs to > disable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1181) Disabling a Job from the main page
[ https://issues.jenkins-ci.org/browse/JENKINS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-1181. - Assignee: Dieter De Meyer (was: Fred G) Resolution: Fixed Please close or re-open this issue if necessary. > Disabling a Job from the main page > -- > > Key: JENKINS-1181 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1181 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: Dieter De Meyer >Assignee: Dieter De Meyer > > It would be easier to disable a specific Job from the main page that lists all > the available jobs (cfr. link for 'Schedule A Build'), > instead of going to the job and clicking configure and disabling it with the > checkbox and finally saving the configuration. > Or on a separate page that lists the jobs so you can select multiple jobs to > disable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13048) dropdown-viewstabbar: cannot save checkbox 'Show Job Counts'
[ https://issues.jenkins-ci.org/browse/JENKINS-13048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162170#comment-162170 ] Fred G commented on JENKINS-13048: -- Pull request: https://github.com/jenkinsci/dropdown-viewstabbar-plugin/pull/2 > dropdown-viewstabbar: cannot save checkbox 'Show Job Counts' > > > Key: JENKINS-13048 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13048 > Project: Jenkins > Issue Type: Bug > Components: dropdown-viewstabbar >Affects Versions: current > Environment: jenkins 1.454 >Reporter: Bruno Marti >Assignee: jieryn > Attachments: dropdown-viewstabbar.jpg > > > selected checkbox 'Show Job Counts' for Views Tab Bar in general configure > screen wont be saved. It is always un-checked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13048) dropdown-viewstabbar: cannot save checkbox 'Show Job Counts'
[ https://issues.jenkins-ci.org/browse/JENKINS-13048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13048 started by jieryn. > dropdown-viewstabbar: cannot save checkbox 'Show Job Counts' > > > Key: JENKINS-13048 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13048 > Project: Jenkins > Issue Type: Bug > Components: dropdown-viewstabbar >Affects Versions: current > Environment: jenkins 1.454 >Reporter: Bruno Marti >Assignee: jieryn > Attachments: dropdown-viewstabbar.jpg > > > selected checkbox 'Show Job Counts' for Views Tab Bar in general configure > screen wont be saved. It is always un-checked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13679) Test Result column does not work with aggregated test results
[ https://issues.jenkins-ci.org/browse/JENKINS-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-13679. -- Assignee: Jim Bim (was: Fred G) Resolution: Duplicate > Test Result column does not work with aggregated test results > - > > Key: JENKINS-13679 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13679 > Project: Jenkins > Issue Type: Bug > Components: extra-columns >Affects Versions: current > Environment: Jenkins ver. 1.457 > Extra columns plugin 1.2 >Reporter: Jim Bim >Assignee: Jim Bim >Priority: Minor > > If the job has "aggregated test result" configured, the column displays the > correct test results, but the link seems to go to > $job/lastCompletedBuild/testReport/ instead of > $job/lastCompletedBuild/aggregatedTestReport/. Hence, if a user clicks the > link, he/she arrives at the build page instead of the result page and has to > navigate one step further. It's not a big deal, but would be nice to have > this fixed. I guess it's a bit similar to JENKINS-9637. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5754) Aborted builds should report the name of the user that terminated the build
[ https://issues.jenkins-ci.org/browse/JENKINS-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-5754. - Assignee: crwong Resolution: Fixed This issue has been fixed in Jenkins version 1.426. > Aborted builds should report the name of the user that terminated the build > --- > > Key: JENKINS-5754 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5754 > Project: Jenkins > Issue Type: New Feature > Components: gui >Reporter: crwong >Assignee: crwong >Priority: Minor > > If a user terminates a build, the build report page should list the name of > the user that aborted the build (similar to how the name of the user that > started a build is done). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2258) improvements for the web ui
[ https://issues.jenkins-ci.org/browse/JENKINS-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162464#comment-162464 ] Fred G commented on JENKINS-2258: - * While a build is in process, clicking on the progress bar in the "Build Executor Status" table takes the user directly to the console output. * As mentioned before, the columns can be configured. Even for the "All" view (described here: https://wiki.jenkins-ci.org/display/JENKINS/Editing+or+Replacing+the+All+View). * Load time depends on hardware, system load, etc. and has certainly improved in the last three years. => All mentioned issues have been addressed. Please re-open this ticket if you disagree. > improvements for the web ui > --- > > Key: JENKINS-2258 > URL: https://issues.jenkins-ci.org/browse/JENKINS-2258 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: euxx > > There is few inconveniences in the current Hudson web UI. > * "Build History" and "Build Executor Status" bars on the left allow to jump > into the build instance, but I often need to see console for that build. It > would be great to have hyperlink in the list that would allow to open console > right from those bars > * when browser is wide or when it has horizontal scroll bar it is hard to > access > "schedule a build" action on the right. It would be much easier to get to it > if > this action would be next to build status and weather icon. > * on remote connection, navigating between Hudson web pages takes 3..5 seconds > and it doesn't seem like browser cache is used -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2258) improvements for the web ui
[ https://issues.jenkins-ci.org/browse/JENKINS-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-2258. - Assignee: euxx Resolution: Fixed > improvements for the web ui > --- > > Key: JENKINS-2258 > URL: https://issues.jenkins-ci.org/browse/JENKINS-2258 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: euxx >Assignee: euxx > > There is few inconveniences in the current Hudson web UI. > * "Build History" and "Build Executor Status" bars on the left allow to jump > into the build instance, but I often need to see console for that build. It > would be great to have hyperlink in the list that would allow to open console > right from those bars > * when browser is wide or when it has horizontal scroll bar it is hard to > access > "schedule a build" action on the right. It would be much easier to get to it > if > this action would be next to build status and weather icon. > * on remote connection, navigating between Hudson web pages takes 3..5 seconds > and it doesn't seem like browser cache is used -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7929) Add a column with tests results ratio and delta in view
[ https://issues.jenkins-ci.org/browse/JENKINS-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Add a column with tests results ratio and delta in view > --- > > Key: JENKINS-7929 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7929 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current >Reporter: dmichonneau > Fix For: current > > > Could we have new columns in the main job view displaying (if tests results > available): > - The ratio of tests passed > - The delta of tests result (+n for n tests fixed, -m for m tests failed) > from last build > This would be particulary useful to monitor tests regressions in builds at a > simple glance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7929) Add a column with tests results ratio and delta in view
[ https://issues.jenkins-ci.org/browse/JENKINS-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162465#comment-162465 ] Fred G commented on JENKINS-7929: - The [Extra Columns Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Extra+Columns+Plugin] provides a test result column. It shows the same output as on the project page. No ratio yet, but this could easily be added. > Add a column with tests results ratio and delta in view > --- > > Key: JENKINS-7929 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7929 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current >Reporter: dmichonneau > Fix For: current > > > Could we have new columns in the main job view displaying (if tests results > available): > - The ratio of tests passed > - The delta of tests result (+n for n tests fixed, -m for m tests failed) > from last build > This would be particulary useful to monitor tests regressions in builds at a > simple glance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7929) Add a column with tests results ratio and delta in view
[ https://issues.jenkins-ci.org/browse/JENKINS-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-7929. - Assignee: dmichonneau Resolution: Fixed > Add a column with tests results ratio and delta in view > --- > > Key: JENKINS-7929 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7929 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current >Reporter: dmichonneau >Assignee: dmichonneau > Fix For: current > > > Could we have new columns in the main job view displaying (if tests results > available): > - The ratio of tests passed > - The delta of tests result (+n for n tests fixed, -m for m tests failed) > from last build > This would be particulary useful to monitor tests regressions in builds at a > simple glance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2255) dashboard access to console for failed builds
[ https://issues.jenkins-ci.org/browse/JENKINS-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162467#comment-162467 ] Fred G commented on JENKINS-2255: - With Jenkins you can just click on the (blue/green/yellow/red) ball in the build history on a job page to get to the console output. This has been implemented in version 1.411. All issues seem to be addressed. Please re-open if you disagree. > dashboard access to console for failed builds > - > > Key: JENKINS-2255 > URL: https://issues.jenkins-ci.org/browse/JENKINS-2255 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: brettcave >Priority: Minor > > From the main hudson dashboard, to get to console output on a failed build > takes > 2 clicks. > 1) click build number from failed build column > 2) click console output > From dashboard, add a link next to the #BUILDNUM in failed column to jump > straight to console to debug the issue. > Or possibly add configuration option to set which page is default when going > to > a build (i.e. status, changes, configure or console output). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2255) dashboard access to console for failed builds
[ https://issues.jenkins-ci.org/browse/JENKINS-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G resolved JENKINS-2255. - Assignee: brettcave Resolution: Fixed > dashboard access to console for failed builds > - > > Key: JENKINS-2255 > URL: https://issues.jenkins-ci.org/browse/JENKINS-2255 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: brettcave >Assignee: brettcave >Priority: Minor > > From the main hudson dashboard, to get to console output on a failed build > takes > 2 clicks. > 1) click build number from failed build column > 2) click console output > From dashboard, add a link next to the #BUILDNUM in failed column to jump > straight to console to debug the issue. > Or possibly add configuration option to set which page is default when going > to > a build (i.e. status, changes, configure or console output). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
[
https://issues.jenkins-ci.org/browse/JENKINS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
> Build Queue does not show the executor a build is waiting for
> -
>
> Key: JENKINS-10468
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10468
> Project: Jenkins
> Issue Type: Bug
> Components: core, gui
> Environment: Jenkins 1.420 on Windows 2003 Server
>Reporter: Martin Ba
>Priority: Minor
>
> I have a Job bound to master. This job has been started by a script and is
> now waiting for execution on master because another Job is running on the
> master (one executor).
> The Build Queue mouseover displays: "Waiting for next available executor on"
> (*no* mention of which node)
> The Build Queue xml api shows:
> {noformat}
>
>
>
>
> Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169402 @
> 2011/07/27 13:10:03
>
>
> Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169419 @
> 2011/07/27 13:21:18
>
>
> false
> true
>
> true
>
> BS-Update-1
> http://-snip-/jenkins/job/BS-Update-1/
> blue
>
> Waiting for next available executor on
>
> 1311772204293
>
>
> {noformat}
> Note how the _why_ is missing the node name.
> Going to the job page however, the Build history is (correctly) displaying:
> "#24 (pending - Waiting for next available executor on master )"
> I have also cross-checked with another job that is also bound to master:
> When I start it manually, the same problem exists wrt. to the non-displayed
> node name.
> (And I assume that the fact that this job is display as "stuck" whereas the
> manually started one isn't, is just to do with how "stuck" is calculated and
> that this job has waited more often or something.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
[
https://issues.jenkins-ci.org/browse/JENKINS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred G reassigned JENKINS-10468:
Assignee: Fred G
> Build Queue does not show the executor a build is waiting for
> -
>
> Key: JENKINS-10468
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10468
> Project: Jenkins
> Issue Type: Bug
> Components: core, gui
> Environment: Jenkins 1.420 on Windows 2003 Server
>Reporter: Martin Ba
>Assignee: Fred G
>Priority: Minor
>
> I have a Job bound to master. This job has been started by a script and is
> now waiting for execution on master because another Job is running on the
> master (one executor).
> The Build Queue mouseover displays: "Waiting for next available executor on"
> (*no* mention of which node)
> The Build Queue xml api shows:
> {noformat}
>
>
>
>
> Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169402 @
> 2011/07/27 13:10:03
>
>
> Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169419 @
> 2011/07/27 13:21:18
>
>
> false
> true
>
> true
>
> BS-Update-1
> http://-snip-/jenkins/job/BS-Update-1/
> blue
>
> Waiting for next available executor on
>
> 1311772204293
>
>
> {noformat}
> Note how the _why_ is missing the node name.
> Going to the job page however, the Build history is (correctly) displaying:
> "#24 (pending - Waiting for next available executor on master )"
> I have also cross-checked with another job that is also bound to master:
> When I start it manually, the same problem exists wrt. to the non-displayed
> node name.
> (And I assume that the fact that this job is display as "stuck" whereas the
> manually started one isn't, is just to do with how "stuck" is calculated and
> that this job has waited more often or something.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
[
https://issues.jenkins-ci.org/browse/JENKINS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162474#comment-162474
]
Fred G commented on JENKINS-10468:
--
The huge long string of random characters that Frank describes is probably
caused by my recent commit:
https://github.com/jenkinsci/jenkins/commit/ff4b02559534c4c67ef95a13defcd7a4fc850a1b
I already opened up a pull request to fix this issue. Sorry for the
inconveniences caused.
> Build Queue does not show the executor a build is waiting for
> -
>
> Key: JENKINS-10468
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10468
> Project: Jenkins
> Issue Type: Bug
> Components: core, gui
> Environment: Jenkins 1.420 on Windows 2003 Server
>Reporter: Martin Ba
>Priority: Minor
>
> I have a Job bound to master. This job has been started by a script and is
> now waiting for execution on master because another Job is running on the
> master (one executor).
> The Build Queue mouseover displays: "Waiting for next available executor on"
> (*no* mention of which node)
> The Build Queue xml api shows:
> {noformat}
>
>
>
>
> Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169402 @
> 2011/07/27 13:10:03
>
>
> Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169419 @
> 2011/07/27 13:21:18
>
>
> false
> true
>
> true
>
> BS-Update-1
> http://-snip-/jenkins/job/BS-Update-1/
> blue
>
> Waiting for next available executor on
>
> 1311772204293
>
>
> {noformat}
> Note how the _why_ is missing the node name.
> Going to the job page however, the Build history is (correctly) displaying:
> "#24 (pending - Waiting for next available executor on master )"
> I have also cross-checked with another job that is also bound to master:
> When I start it manually, the same problem exists wrt. to the non-displayed
> node name.
> (And I assume that the fact that this job is display as "stuck" whereas the
> manually started one isn't, is just to do with how "stuck" is calculated and
> that this job has waited more often or something.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant
[ https://issues.jenkins-ci.org/browse/JENKINS-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-8916 started by Fred G. > Allowing same type of parameter for triggered build more than once seems > redundant > -- > > Key: JENKINS-8916 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8916 > Project: Jenkins > Issue Type: Bug > Components: parameterized-trigger >Affects Versions: current >Reporter: Fred G >Assignee: Fred G >Priority: Minor > > While working on [JENKINS-7377] I noticed that it's redundant and confusing > to allow the same type of parameter for a triggered build more than once. > For example, right now it's possible to specify "Current Build Parameters", > or "Subversion Revision" two or more times. > The only type where it might make sense is "Parameters from properties file". > I think for every type of parameters a simple checkbox is sufficient. > I'll try to make the necessary changes and open a pull request, but > appreciate comments or criticism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant
[ https://issues.jenkins-ci.org/browse/JENKINS-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reassigned JENKINS-8916: --- Assignee: Fred G (was: huybrechts) > Allowing same type of parameter for triggered build more than once seems > redundant > -- > > Key: JENKINS-8916 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8916 > Project: Jenkins > Issue Type: Bug > Components: parameterized-trigger >Affects Versions: current >Reporter: Fred G >Assignee: Fred G >Priority: Minor > > While working on [JENKINS-7377] I noticed that it's redundant and confusing > to allow the same type of parameter for a triggered build more than once. > For example, right now it's possible to specify "Current Build Parameters", > or "Subversion Revision" two or more times. > The only type where it might make sense is "Parameters from properties file". > I think for every type of parameters a simple checkbox is sufficient. > I'll try to make the necessary changes and open a pull request, but > appreciate comments or criticism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant
[ https://issues.jenkins-ci.org/browse/JENKINS-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162475#comment-162475 ] Fred G commented on JENKINS-8916: - Pull request: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/20 > Allowing same type of parameter for triggered build more than once seems > redundant > -- > > Key: JENKINS-8916 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8916 > Project: Jenkins > Issue Type: Bug > Components: parameterized-trigger >Affects Versions: current >Reporter: Fred G >Assignee: Fred G >Priority: Minor > > While working on [JENKINS-7377] I noticed that it's redundant and confusing > to allow the same type of parameter for a triggered build more than once. > For example, right now it's possible to specify "Current Build Parameters", > or "Subversion Revision" two or more times. > The only type where it might make sense is "Parameters from properties file". > I think for every type of parameters a simple checkbox is sufficient. > I'll try to make the necessary changes and open a pull request, but > appreciate comments or criticism. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reopened JENKINS-12598: -- Sorry for reopening this issue. I tested version 2.4-SNAPSHOT. During the upgrade from version 2.3 all module configurations got lost. So I had to cumbersomely add modules and reinsert each module name. Before 2.4 is publicly released we should try to implement an automated migration mechanism, otherwise we risk another user/dev list bashing. I still think the user should have the choice between an individual and list-oriented module configuration. > In 2.0 update you need to specify branch for every module > - > > Key: JENKINS-12598 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12598 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Reporter: Ulli Hafner >Assignee: Michael Clarke >Priority: Critical > Attachments: Jenkins_CvsPluginModules.png, > repositoryLocationProposal.png > > > After an upgrade to the new 2.0 version of the cvs plug-in we now need to > specify the "Module location" (trunk, branch) for each module. This is quite > cumbersome if you have a lot of modules. In the 1.x plug-in releases you are > able to select a given branch for all modules in one text field. > While I think the new "feature" has a lot of use cases (i.e., having trunk > and branches mixed), the usability could be improved here. My requirement is > to select/change the branch (or trunk) for all modules in a simple way. > A non-Ajax suggestion would be to have a "default" entry in the Selection, > i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at > the top of the cvs configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13189) Support the Test Result for a project that uses TAP
Fred G commented on JENKINS-13189 Support the Test Result for a project that uses TAP I'd like to keep the extra-columns plugin free of dependencies on other plugins. Maybe the TAP plugin can instead re-use the test result API in Jenkins core. 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-8916) Allowing same type of parameter for triggered build more than once seems redundant
Fred G commented on JENKINS-8916 Allowing same type of parameter for triggered build more than once seems redundant Yes, that's the only drawback with this solution. Do you have a use-case where you need to specify multiple property files? 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-8916) Allowing same type of parameter for triggered build more than once seems redundant
Fred G assigned JENKINS-8916 to Daniel Beck Allowing same type of parameter for triggered build more than once seems redundant Change By: Fred G (08/Jul/12 1:45 PM) Assignee: Fred G Daniel Beck 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-60937) Pods are not created due to 'invalid label value: "jenkins/slave-default"'
Title: Message Title Fred G created an issue Jenkins / JENKINS-60937 Pods are not created due to 'invalid label value: "jenkins/slave-default"' Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-01-31 12:47 Environment: kubernetes-plugin 1.22.1 and following Jenkins LTS 2.190.1 configuration-as-code-plugin Labels: regression Priority: Major Reporter: Fred G Since upgrading to version 1.22.1 and higher of the kubernetes-plugin pods are not created (and therefore builds are not starting) due to the following error: Failed to count the # of live instances on Kubernetes io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://172.30.40.1/api/v1/namespaces/rdf4j/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Djenkins%2Fslave-default. Message: unable to parse requirement: invalid label value: "jenkins/slave-default": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?'). Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=unable to parse requirement: invalid label value: "jenkins/slave-default": a valid label must be an empty string or consist of alphanumeric characters, '
[JIRA] (JENKINS-60937) Pods are not created due to 'invalid label value: "jenkins/slave-default"'
Title: Message Title Fred G commented on JENKINS-60937 Re: Pods are not created due to 'invalid label value: "jenkins/slave-default"' PR: https://github.com/jenkinsci/kubernetes-plugin/pull/700 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204334.1580474864000.9488.1580479560071%40Atlassian.JIRA.
[JIRA] (JENKINS-61186) Add lastBuild/consoleFull#footer as an option
Title: Message Title Fred G commented on JENKINS-61186 Re: Add lastBuild/consoleFull#footer as an option Sounds reasonable. Please open a pull request for this. If required, I'm happy to help. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204730.1582326298000.1591.1582977600249%40Atlassian.JIRA.
[JIRA] (JENKINS-61186) Add lastBuild/consoleFull#footer as an option
Title: Message Title Fred G started work on JENKINS-61186 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204730.1582326298000.1593.1582977600283%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Fred G commented on JENKINS-59485 Re: Trust level "Contributors" is ambiguous, should be called "Collaborators" instead PR has been created: https://github.com/jenkinsci/github-branch-source-plugin/pull/283 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202100.1569247714000.1908.1583026020388%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Fred G assigned an issue to Liam Newman Jenkins / JENKINS-59485 Trust level "Contributors" is ambiguous, should be called "Collaborators" instead Change By: Fred G Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202100.1569247714000.1910.1583026020438%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Fred G updated an issue Jenkins / JENKINS-61294 Jenkins node disconnects frequently because of that job fails. Change By: Fred G Component/s: core Component/s: build-node-column-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204871.1583165063000.3148.1583196480265%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Fred G assigned an issue to Unassigned Jenkins / JENKINS-61294 Jenkins node disconnects frequently because of that job fails. Change By: Fred G Assignee: Fred G Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204871.1583165063000.3150.1583196480299%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Fred G commented on JENKINS-61294 Re: Jenkins node disconnects frequently because of that job fails. It's not clear why this issue was assigned to the build-node-column-plugin component, therefore reassigning to core and unassigning myself. Please also provide more context about the master and the build agent. Which OS? Java version? etc. Did this issue exist from the beginning? Did it appear suddenly? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204871.1583165063000.3152.1583196660142%40Atlassian.JIRA.
[JIRA] (JENKINS-37071) extra-columns: last build number
Title: Message Title Fred G commented on JENKINS-37071 Re: extra-columns: last build number Sorry, this one fell through the cracks. I'm not planning to implement this in the foreseeable future, therefore I'm closing this ticket. It should be fairly simple to implement by copying an existing column and retrieving the last build number from the API. If you still think this is valuable (after 3 years ), please re-open this issue and I'd be happy to review a pull request and help you along the way. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173143.1469822529000.5565.1566238200425%40Atlassian.JIRA.
[JIRA] (JENKINS-37071) extra-columns: last build number
Title: Message Title Fred G closed an issue as Won't Do Jenkins / JENKINS-37071 extra-columns: last build number Change By: Fred G Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173143.1469822529000.5573.1566238200618%40Atlassian.JIRA.
[JIRA] (JENKINS-36632) Pipeline support
Title: Message Title Fred G closed an issue as Fixed This was fixed by changes in Jenkins core quite a while ago. I've successfully tested this with Jenkins v2.138.4 LTS, but it probably works with lower versions as Jesse mentioned. Jenkins / JENKINS-36632 Pipeline support Change By: Fred G Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172660.1468360684000.5607.1566239040606%40Atlassian.JIRA.
[JIRA] (JENKINS-59119) Terminating xvnc takes several minutes when running on Kubernetes agents
Title: Message Title
Fred G created an issue
Jenkins / JENKINS-59119
Terminating xvnc takes several minutes when running on Kubernetes agents
Issue Type:
Bug
Assignee:
Levon Saldamli
Components:
core, xvnc-plugin
Created:
2019-08-28 11:48
Environment:
Jenkins version 2.176.2 LTS OpenShift 3.9 cluster
Priority:
Minor
Reporter:
Fred G
At the end of a build, it seems to hang for several minutes while Xvnc is shutting down ("Terminating xvnc."). Several observations:
This only happens on dynamic agents running on our OpenShift cluster. It does not happen on static/dedicated build agents or when running on a Jenkins master.
It takes ~6 minutes to terminate when the option "Create a dedicated Xauthority file per build" is enabled. It takes "only" ~2 minutes when this option is disabled. This was reproducible across several builds switching the option on and off.
I was able to narrow down the problem to this line in the code:
launcher.kill(xauthorityEnv);
https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L240
Since it
[JIRA] (JENKINS-54240) buildDescription column not available for jobDSL
Title: Message Title Fred G commented on JENKINS-54240 Re: buildDescription column not available for jobDSL Daniel Spilker can you help here? What needs to be added to make this and other columns available in the JobDSL plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194881.1540455514000.3916.1567339560206%40Atlassian.JIRA.
[JIRA] (JENKINS-54240) buildDescription column not available for jobDSL
Title: Message Title Fred G commented on JENKINS-54240 Re: buildDescription column not available for jobDSL Good to hear that the Dynamic DSL can be used. Just out of curiosity, how would one add a column so it's available in the JobDSL plugin without using the Dynamic DSL? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194881.1540455514000.333.1568066280187%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Fred G created an issue Jenkins / JENKINS-59485 Trust level "Contributors" is ambiguous, should be called "Collaborators" instead Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-09-23 14:08 Priority: Minor Reporter: Fred G The "Discover pull requests from forks" allows to set a trust level. The trust level "Contributors" is ambiguous, since it does not refer to all contributors, but actually only to collaborators (in the GitHub definition of collaborators => https://developer.github.com/v3/repos/collaborators/ ). Since GitHub collaborators have to be explicitly added to a repo, this is usually a smaller group of people. This ambiguity is somewhat explained in the info/help text (when you click on the icon left of the trust drop-down menu), but I'd recommend to make it clearer by renaming the entry in the drop-down to "Collaborator" or even "GitHub Collaborator". I don't see a value in using a different term for it. Actual examples of misunderstanding: https://bugs.eclipse.org/bugs/show_bug.cgi?id=549571 https://bugs.eclipse.org/bugs/show_bug.cgi?id=550512#c12 Add Comment
[JIRA] (JENKINS-54567) Last deployed/published/finished column
Title: Message Title Fred G started work on JENKINS-54567 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195346.1541871979000.6999.1569627120177%40Atlassian.JIRA.
[JIRA] (JENKINS-54567) Last deployed/published/finished column
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding a new configurable column called "Last Build". Jenkins / JENKINS-54567 Last deployed/published/finished column Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit htt
[JIRA] (JENKINS-29655) Last build
Title: Message Title Fred G started work on JENKINS-29655 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164134.1438009468000.7003.1569627300230%40Atlassian.JIRA.
[JIRA] (JENKINS-29655) Last build
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding a new configurable column called "Last Build". Jenkins / JENKINS-29655 Last build Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgi
[JIRA] (JENKINS-20953) Suggestion: "Last Build Time" column
Title: Message Title Fred G started work on JENKINS-20953 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152475.1386742549000.7013.1569627420979%40Atlassian.JIRA.
[JIRA] (JENKINS-20953) Suggestion: "Last Build Time" column
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding a new configurable column called "Last Build". Jenkins / JENKINS-20953 Suggestion: "Last Build Time" column Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https:
[JIRA] (JENKINS-43605) ability to specify parameters to show and parameters to exclude for a view
Title: Message Title Fred G started work on JENKINS-43605 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180930.1492189451000.7023.1569627540163%40Atlassian.JIRA.
[JIRA] (JENKINS-43605) ability to specify parameters to show and parameters to exclude for a view
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21 by adding regex filters to the configuration of the build parameter column. Jenkins / JENKINS-43605 ability to specify parameters to show and parameters to exclude for a view Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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...@googlegr
[JIRA] (JENKINS-51171) Use Regex to filter for an Buildparameter
Title: Message Title Fred G started work on JENKINS-51171 Change By: Fred G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190479.1525682766000.7027.1569627720315%40Atlassian.JIRA.
[JIRA] (JENKINS-51171) Use Regex to filter for an Buildparameter
Title: Message Title Fred G resolved as Fixed Fixed in version 1.21. Jenkins / JENKINS-51171 Use Regex to filter for an Buildparameter Change By: Fred G Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.1
[JIRA] (JENKINS-57141) Multiple Build Duration Columns resets values when returning to Edit View
Title: Message Title Fred G updated JENKINS-57141 Fixed in version 1.21. Jenkins / JENKINS-57141 Multiple Build Duration Columns resets values when returning to Edit View Change By: Fred G Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.
