[JIRA] [core] (JENKINS-25488) New UI wastes horizontal space
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-25488 New UI wastes horizontal space Change By: Manuel Jesús Recena Soto Labels: 2.0-rejected user-experience ux 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] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title Manuel Jesús Recena Soto resolved as Done Jenkins / JENKINS-34047 Sort github repos in case insensitive fashion Change By: Manuel Jesús Recena Soto Status: In Progress Resolved Resolution: Done 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] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34047 Re: Sort github repos in case insensitive fashion Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/007901635d8c82f70d66580168a1149c09850a25 Log: Revert "JENKINS-34047 Case insensitive sorting" 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] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34047 Re: Sort github repos in case insensitive fashion Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/4d1792912c3d87654b5524b83767406d4851c81b Log: Merge pull request #38 from michaelneale/master JENKINS-34047 Case insensitive sorting Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/34259081f6bd...4d1792912c3d 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] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34047 Re: Sort github repos in case insensitive fashion Code changed in jenkins User: Michael Neale Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/d91fd623c2e3c7177a3bb8c69254ea96628f7def Log: cat insensitive sorting for JENKINS-34047 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] [core] (JENKINS-34079) Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell")
Title: Message Title Thawngzapum Lian updated an issue Jenkins / JENKINS-34079 Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell") Change By: Thawngzapum Lian Please note that the aforementioned issue was not found in Version 1.579.The issue surfaced after upgrade to Version 1.653 Python pexpect process wrapped in a python script always timeout on lengthy process when running it via Jenkins (under "Execute Shell"). The same script successfully ran when directly running it on console terminal. Can Jenkins shell can be run under pseudo terminal slave (pts/N)?Python script as run as belowpython python-script.py --param1= --param2=Python pexpect process was instantiated in python-script.pyMonitoring the process (Manual run vs. Jenkins run)Jenkins run (Script did NOT run OK)UID PID PPID C STIME TTY TIME CMDroot 11909 31184 0 21:52 ? 00:00:00 /bin/sh -xe /tmp/hudson2869108017601047728.shManual Run (Script ran OK)root 2356 18925 0 21:00 pts/000:00:01 /bin/sh -xe /tmp/hudson2869108017601047728.sh 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] [core] (JENKINS-34079) Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell")
Title: Message Title Thawngzapum Lian created an issue Jenkins / JENKINS-34079 Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell") Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/07 3:13 AM Environment: Red Hat Enterprise Linux Server release 7.2 (Maipo) Jenkins Version 1.653 The aforementioned issue was not found in Version 1.579 Priority: Major Reporter: Thawngzapum Lian Python pexpect process wrapped in a python script always timeout on lengthy process when running it via Jenkins (under "Execute Shell"). The same script successfully ran when directly running it on console terminal. Can Jenkins shell can be run under pseudo terminal slave (pts/N)? Python script as run as below python python-script.py --param1= --param2= Python pexpect process was instantiated in python-script.py Monitoring the process (Manual run vs. Jenkins run) Jenkins run (Script did NOT run OK) UID PID PPID C STIME TTY TIME CMD root 11909 31184 0 21:52 ? 00:00:00 /bin/sh -xe /tmp/hudson2869108017601047728.sh Manual Run (Script ran OK) root 2356 18925 0 21:00 pts/0 00:00:01
[JIRA] [multi-branch-project-plugin] (JENKINS-34078) Multibranch Plugin: Deprecated annotations
Title: Message Title Alastair D'Silva created an issue Jenkins / JENKINS-34078 Multibranch Plugin: Deprecated annotations Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Apr/07 3:11 AM Priority: Minor Reporter: Alastair D'Silva The following deprecations are reported when compiling: [ERROR] /home/adsilva/src/multi-branch-project-plugin/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/AbstractMultiBranchProject.java:[317,5] [deprecation] NonNull in edu.umd.cs.findbugs.annotations has been deprecated [ERROR] /home/adsilva/src/multi-branch-project-plugin/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/AbstractMultiBranchProject.java:[329,36] [deprecation] CheckForNull in edu.umd.cs.findbugs.annotations has been deprecated [ERROR] /home/adsilva/src/multi-branch-project-plugin/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/AbstractMultiBranchProject.java:[330,66] [deprecation] CheckForNull in edu.umd.cs.findbugs.annotations has been deprecated [ERROR] /home/adsilva/src/multi-branch-project-plugin/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/AbstractMultiBranchProject.java:[341,36] [deprecation] NonNull in edu.umd.cs.findbugs.annotations has been deprecated [ERROR] /home/adsilva/src/multi-branch-project-plugin/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/AbstractMultiBranchProject.java:[349,36] [deprecation] CheckForNull in edu.umd.cs.findbugs.annotations has been deprecated [ERROR] /home/adsilva/src/multi-branch-project-plugin/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/AbstractMultiBranchProject.java:[350,51] [deprecation] NonNull in
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33624) Improve performance of Pipeline Stage View even with very long FlowGraphs
Title: Message Title Sam Van Oort resolved as Fixed Jenkins / JENKINS-33624 Improve performance of Pipeline Stage View even with very long FlowGraphs Change By: Sam Van Oort Status: In Progress Resolved 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] [delivery-pipeline-plugin] (JENKINS-34077) Problem with master branch code, when running it is not showing DPP configuration
Title: Message Title Suresh Kumar created an issue Jenkins / JENKINS-34077 Problem with master branch code, when running it is not showing DPP configuration Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Apr/07 2:50 AM Priority: Minor Reporter: Suresh Kumar After forking the project and running locally, the component configuration is not coming up and there is no DPP view option to create. Are there any changes happened to master branch code. Add Comment
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33624) Improve performance of Pipeline Stage View even with very long FlowGraphs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33624 Re: Improve performance of Pipeline Stage View even with very long FlowGraphs Code changed in jenkins User: Sam Van Oort Path: rest-api/pom.xml rest-api/src/main/java/com/cloudbees/workflow/flownode/FlowNodeExecutorNameCache.java rest-api/src/main/java/com/cloudbees/workflow/flownode/FlowNodeListCacheAction.java rest-api/src/main/java/com/cloudbees/workflow/flownode/FlowNodeNavigationListener.java rest-api/src/main/java/com/cloudbees/workflow/flownode/FlowNodeUtil.java rest-api/src/main/java/com/cloudbees/workflow/rest/AbstractAPIActionHandler.java rest-api/src/main/java/com/cloudbees/workflow/rest/endpoints/FlowNodeAPI.java rest-api/src/main/java/com/cloudbees/workflow/rest/endpoints/RunAPI.java rest-api/src/main/java/com/cloudbees/workflow/rest/endpoints/flownode/Describe.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/AtomFlowNodeExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/FlowNodeExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/RunExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/StageNodeExt.java rest-api/src/main/java/com/cloudbees/workflow/util/ModelUtil.java rest-api/src/test/java/com/cloudbees/workflow/flownode/FlowNodeUtilTest.java rest-api/src/test/java/com/cloudbees/workflow/rest/endpoints/JobAndRunAPITest.java ui/pom.xml http://jenkins-ci.org/commit/pipeline-stage-view-plugin/488fe8b0170f9affc49a8e4169f74e34a21a97c4 Log: Merge pull request #4 from jenkinsci/optimize-flow-walking JENKINS-33624 Improve Perfomance with Large Pipelines Compare: https://github.com/jenkinsci/pipeline-stage-view-plugin/compare/360909b3b6b9...488fe8b0170f 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
[JIRA] [multi-branch-project-plugin] (JENKINS-34076) Multibranch projects no longer sync changes from parent project to branches
Title: Message Title Alastair D'Silva created an issue Jenkins / JENKINS-34076 Multibranch projects no longer sync changes from parent project to branches Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Apr/07 2:07 AM Environment: Jenkins 1.650 Folders Plugin 5.6 Priority: Major Reporter: Alastair D'Silva After updating to 5.6 of the folder plugin, changes to the parent project no longer sync to the branches, instead, each branch says "ignoring duplicate " I suspect it is related to Jenkins-32179: https://github.com/jenkinsci/cloudbees-folder-plugin/commit/30f744250762bf9472cd269a0bef4a597203be01 Add Comment
[JIRA] [git-plugin] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Mark Waite commented on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) You might try using the local branch extension that was added in git plugin 2.4.4. It may be able to checkout the branch which matches the name from the branch spec, rather than reporting the name of the first branch mentioned in the rev-parse output. 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] [email-ext-plugin] (JENKINS-34022) Jenkins wont send email triggered by a job while sending test email
Title: Message Title Alex Earl commented on JENKINS-34022 Re: Jenkins wont send email triggered by a job while sending test email Can you enable debug mode for email-ext in the global configuration and post the console output for the job? There should be more information. 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated AnneTheAgile this is not yet implemented in any official release of the Jenkins git plugin. It is a large enough change that I wanted an extended beta period to test it. Breaking the authentication techniques of a plugin used in 60 000 installations was too scary for me to not want an extended beta period. I'm not sure why you say that the "2.5 experimental patch ... is no longer on the beta". I just configured a fresh installed Jenkins to use the experimental plugins update center and confirmed that git plugin 2.5.0-beta4 is available there, as is git client plugin 1.20.0-beta3. The git plugin changelog includes references to git plugin beta versions 2.5.0-beta1, 2.5.0-beta2, and 2.5.0-beta3. Sorry, I forgot to publish an update to describe 2.5.0-beta4 on the wiki. The git client plugin changelog includes references to git client plugin beta versions 1.20.0-beta1 and 1.20.0-beta3. Could you try the experimental update center to see if it shows you the same thing it shows me? 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] [core] (JENKINS-33810) Release 2.0 Release Candidate
Title: Message Title Daniel Beck resolved as Fixed KK is releasing the 2.0 RC right now. Jenkins / JENKINS-33810 Release 2.0 Release Candidate Change By: Daniel Beck Status: Open Resolved 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] [ansicolor-plugin] (JENKINS-29090) Too many span labels for the same line
Title: Message Title Steve Peters commented on JENKINS-29090 Re: Too many span labels for the same line Sorry for the delayed response. Yes, our ANSI output has the same formatting; the html just inflates it a bit. Perhaps this could be a feature request to merge adjacent span elements with identical colors? 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Title: Message Title
Patrice Matignon commented on JENKINS-26210
Re: Configure Jobs to be hidden from the delivery pipeline
FWIW, I think this is closed a bit unfairly. This proposed code change doesn't alter the default behavior, where all the jobs will be shown. It only kicks in when the pipeline is configured to specifically hide jobs. I think the use case(s) for it were laid out pretty convincingly, I know that some jobs in my pipelines have no value for the target audience and are therefore distracting/confusing. Also, there were some suggestions to ease some of the given concerns - mine was to have a blinking indicator ("hidden job running") on the pipeline instance, when a hidden job is executing in the background. It can be easily adapted to show a status (red/blue) as well as a toggle button to show the hidden jobs if desired. Design-wise, if a job is preferred to be hidden, it probably doesn't matter to the pipeline audience whether it succeeded or failed. For my use cases, the jobs I want to hide are not in-between visible jobs, they are side-branches or leaves of the pipeline tree anyway. It would not be making a lot of sense to hide jobs on the pipeline critical path(s) I'd have to agree.
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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title AnneTheAgile edited a comment on JENKINS-20941 Re: Stored git credentials not used when submodule is updated As I see it; 1.The Jenkins Git plugin ticket is not solved anywhere yet, the best I can see. The v2.5 experimental patch was not accepted, is no longer on the beta, and the last release is 2.4.4. Its PR was closed, not implemented in favor of an edit to the credentials plugin. https://issues.jenkins-ci.org/browse/JENKINS-20941 https://github.com/jenkinsci/git-plugin/pull/342 2.The Jenkins Credentials plugin PR has similarly not been accepted (but it needs work so is not standalone). https://github.com/jenkinsci/ git credentials -plugin/pull/ 342 32 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title AnneTheAgile commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated As I see it; 1.The Jenkins Git plugin ticket is not solved anywhere yet, the best I can see. The v2.5 experimental patch was not accepted, is no longer on the beta, and the last release is 2.4.4. Its PR was closed, not implemented in favor of an edit to the credentials plugin. https://issues.jenkins-ci.org/browse/JENKINS-20941 2.The Jenkins Credentials plugin PR has similarly not been accepted (but it needs work so is not standalone). https://github.com/jenkinsci/git-plugin/pull/342 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] [core] (JENKINS-32340) Cannot enable disabled dependencies
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-32340 Cannot enable disabled dependencies Not for 2.0, and probably not for 2.1 if 2072 gets reinstated. Change By: Daniel Beck Priority: Blocker Major Labels: 2.0-planned lts-candidate 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] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Fail a plugin if its dependencies doesn't exist Code changed in jenkins User: Daniel Beck Path: changelog.html core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/PluginWrapper.java test/src/test/java/hudson/PluginManagerTest.java test/src/test/java/hudson/PluginManagerUtil.java test/src/test/java/hudson/PluginWrapperTest.java test/src/test/resources/plugins/dependee-0.0.2.hpi test/src/test/resources/plugins/depender-0.0.2.hpi test/src/test/resources/plugins/mandatory-depender-0.0.2.hpi http://jenkins-ci.org/commit/jenkins/1e338d3565c8c58d2556f344a7c34a3b3ab18ca3 Log: Merge pull request #2236 from daniel-beck/JENKINS-34073 JENKINS-34073 Revert fix for JENKINS-21486 Compare: https://github.com/jenkinsci/jenkins/compare/25340e033b5d...1e338d3565c8 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] [core] (JENKINS-34073) Plugin dependency fix (JENKINS-21486) not visible enough
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34073 Re: Plugin dependency fix (JENKINS-21486) not visible enough Code changed in jenkins User: Daniel Beck Path: changelog.html core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/PluginWrapper.java test/src/test/java/hudson/PluginManagerTest.java test/src/test/java/hudson/PluginManagerUtil.java test/src/test/java/hudson/PluginWrapperTest.java test/src/test/resources/plugins/dependee-0.0.2.hpi test/src/test/resources/plugins/depender-0.0.2.hpi test/src/test/resources/plugins/mandatory-depender-0.0.2.hpi http://jenkins-ci.org/commit/jenkins/1e338d3565c8c58d2556f344a7c34a3b3ab18ca3 Log: Merge pull request #2236 from daniel-beck/JENKINS-34073 JENKINS-34073 Revert fix for JENKINS-21486 Compare: https://github.com/jenkinsci/jenkins/compare/25340e033b5d...1e338d3565c8 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] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Fail a plugin if its dependencies doesn't exist Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginWrapper.java http://jenkins-ci.org/commit/jenkins/4d0143b8d2be4888d889de44cbc8eccb8776bd41 Log: Revert "Merge pull request #2228 from Vlatombe/ JENKINS-21486 -follow-up" This reverts commit 0846358bf62730a00cfed412b9e8bc0dc7cc1f8a, reversing changes made to 2c9adc9965e2fb1ebb4402e4f7307a5d8eae1912. 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] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Fail a plugin if its dependencies doesn't exist Code changed in jenkins User: Daniel Beck Path: changelog.html core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/PluginWrapper.java test/src/test/java/hudson/PluginManagerTest.java test/src/test/java/hudson/PluginManagerUtil.java test/src/test/java/hudson/PluginWrapperTest.java test/src/test/resources/plugins/dependee-0.0.2.hpi test/src/test/resources/plugins/depender-0.0.2.hpi test/src/test/resources/plugins/mandatory-depender-0.0.2.hpi http://jenkins-ci.org/commit/jenkins/70ee2012e901214e98c5c24ccf42c8a3af2b7647 Log: Revert "[FIXED JENKINS-21486] Merged #2172: enforce plugin dependencies."< /p> This reverts commit fa39668b814a6c51e7c460f529692b149e835fc0, reversing changes made to be9bc0dba552e271b47102292fc9f585afaaf212. 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] [core] (JENKINS-33364) All UI fields in core Jenkins should have English documentation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33364 Re: All UI fields in core Jenkins should have English documentation Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/AbstractItem/help-slaveAffinity.html core/src/main/resources/hudson/model/AbstractProject/help-concurrentBuild.html core/src/main/resources/hudson/model/AbstractProject/help-label.html core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/Messages_en_GB.properties core/src/main/resources/hudson/model/Messages_it.properties core/src/main/resources/hudson/model/ParametersDefinitionProperty/help.html core/src/main/resources/jenkins/model/BuildDiscarderProperty/help.html core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html core/src/main/resources/jenkins/model/Messages.properties core/src/main/resources/lib/hudson/project/config-disableBuild.jelly core/src/main/resources/lib/hudson/project/config-disableBuild_bg.properties core/src/main/resources/lib/hudson/project/config-disableBuild_da.properties core/src/main/resources/lib/hudson/project/config-disableBuild_de.properties core/src/main/resources/lib/hudson/project/config-disableBuild_es.properties core/src/main/resources/lib/hudson/project/config-disableBuild_fr.properties core/src/main/resources/lib/hudson/project/config-disableBuild_he.properties core/src/main/resources/lib/hudson/project/config-disableBuild_hu.properties core/src/main/resources/lib/hudson/project/config-disableBuild_it.properties core/src/main/resources/lib/hudson/project/config-disableBuild_ja.properties core/src/main/resources/lib/hudson/project/config-disableBuild_ko.properties core/src/main/resources/lib/hudson/project/config-disableBuild_lt.properties core/src/main/resources/lib/hudson/project/config-disableBuild_nb_NO.properties core/src/main/resources/lib/hudson/project/config-disableBuild_nl.properties core/src/main/resources/lib/hudson/project/config-disableBuild_pl.properties core/src/main/resources/lib/hudson/project/config-disableBuild_pt_BR.properties core/src/main/resources/lib/hudson/project/config-disableBuild_ro.properties core/src/main/resources/lib/hudson/project/config-disableBuild_ru.properties core/src/main/resources/lib/hudson/project/config-disableBuild_sk.properties core/src/main/resources/lib/hudson/project/config-disableBuild_sv_SE.properties core/src/main/resources/lib/hudson/project/config-disableBuild_tr.properties core/src/main/resources/lib/hudson/project/config-disableBuild_uk.properties core/src/main/resources/lib/hudson/project/config-disableBuild_zh_CN.properties core/src/main/resources/lib/hudson/project/config-disableBuild_zh_TW.properties war/src/main/webapp/help/project-config/disable.html war/src/main/webapp/help/project-config/scmCheckoutRetryCount.html http://jenkins-ci.org/commit/jenkins/25340e033b5dd27657803caab5dd60b33b67215c Log: Merge pull request #2137 from orrc/JENKINS-33364_freestyle-config JENKINS-33364 Core documentation: Freestyle project config Compare: https://github.com/jenkinsci/jenkins/compare/4cb3f4eb27c1...25340e033b5d Add Comment
[JIRA] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title M Chon created an issue Jenkins / JENKINS-34075 Getting "Invalid id:" error when trying to create a very simple changelog Issue Type: Bug Assignee: Paul Wellner Bou Attachments: git-changelog-config.PNG Components: git-changelog-plugin Created: 2016/Apr/06 10:58 PM Environment: Ubuntu 14.04 Priority: Minor Reporter: M Chon I installed the latest version of the plugin. I then attempted to configure it to handle the most simple case possible; generating a CHANGELOG.txt file based on the difference between $GIT_PREVIOUS_COMMIT and $GIT_COMMIT I get this error. Here is the console log: Checking out Revision 67e061dcfa6c9edf6fce28c40939418a0c334ea3 (origin/foo) > git config core.sparsecheckout # timeout=10 > git checkout -f 67e061dcfa6c9edf6fce28c40939418a0c334ea3 > git rev-list 67e061dcfa6c9edf6fce28c40939418a0c334ea3 # timeout=10 [workspace] $ /bin/sh -xe /tmp/hudson770153796434746119.sh + echo GIT_COMMIT is 67e061dcfa6c9edf6fce28c40939418a0c334ea3
[JIRA] [script-security-plugin] (JENKINS-27725) Cannot use Date class when workflow script is sandboxed
Title: Message Title Roy Tinker commented on JENKINS-27725 Re: Cannot use Date class when workflow script is sandboxed I'm still seeing this issue. I'm using script-security 1.18. 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] [promoted-builds-plugin] (JENKINS-34074) Email-Notification doesn't appear correctly under Actions
Title: Message Title
David Chou created an issue
Jenkins / JENKINS-34074
Email-Notification doesn't appear correctly under Actions
Issue Type:
Bug
Assignee:
Dennis Schulte
Attachments:
Screen Shot 2016-04-06 at 3.47.26 PM.png, Screen Shot 2016-04-06 at 3.48.12 PM.png
Components:
promoted-builds-plugin
Created:
2016/Apr/06 10:50 PM
Priority:
Minor
Reporter:
David Chou
Using this Groovy snippet below, I was expecting that there would be an "Email-Notification" that is added as part of the build promotion under Actions like this:
properties {
promotions {
promotion {
name("Approved by Release Manager")
icon("Gold Star")
restrict('linuxSlave')
conditions {
manual("Dev Leads") {
parameters{
textParam("Reason","","${PROJECT_NAME} Build Details")
}
}
}
actions {
downstreamParameterized {
trigger("${PROJECT_NAME}-prod-deploy") {
parameters {
currentBuild()
predefinedProp("APPROVED_BY_USER","\${PROMOTED_USER_NAME}")
predefinedProp("APPROVED_STATUS","true")
}
}
}
publishers {
mailer("\${EMAIL_FAILURE_NOTIFICATION}", true, false)
}
[JIRA] [script-security-plugin] (JENKINS-27725) Cannot use Date class when workflow script is sandboxed
Title: Message Title
Roy Tinker edited a comment on JENKINS-27725
Re: Cannot use Date class when workflow script is sandboxed
Minimal failing script: ` {code} input new Date().format('MMM-') ` {code}
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] [script-security-plugin] (JENKINS-27725) Cannot use Date class when workflow script is sandboxed
Title: Message Title
Roy Tinker commented on JENKINS-27725
Re: Cannot use Date class when workflow script is sandboxed
Minimal failing script: `input new Date().format('MMM-')`
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] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Jesse Glick commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Backed out in workflow-cps 2.1. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Hotfix released as 2.1. 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] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/ca821248fbc4ec1ebfa00b059eb8162af843df76 Log: Merge pull request #2 from jglick/JENKINS-34064-backout JENKINS-34064 Backing out JENKINS-26481 fix Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/61fb5860ea27...ca821248fbc4 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] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/b5c85d9f1663b1c34c8e56b656fd0e2cee662869 Log: [FIXED JENKINS-34064] Backing out JENKINS-26481 fix since it broke Pipeline in Jenkins 2.x. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/ca821248fbc4ec1ebfa00b059eb8162af843df76 Log: Merge pull request #2 from jglick/JENKINS-34064-backout JENKINS-34064 Backing out JENKINS-26481 fix Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/61fb5860ea27...ca821248fbc4 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] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/b5c85d9f1663b1c34c8e56b656fd0e2cee662869 Log: [FIXED JENKINS-34064] Backing out JENKINS-26481 fix since it broke Pipeline in Jenkins 2.x. 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] [core] (JENKINS-34073) Plugin dependency fix (JENKINS-21486) not visible enough
Title: Message Title Daniel Beck commented on JENKINS-34073 Re: Plugin dependency fix (JENKINS-21486) not visible enough It's too late to write and test an adequate UI for 2.0 RC, this should be rolled back and addressed properly in a subsequent release (2.1 would be fine for me). 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] [core] (JENKINS-34073) Plugin dependency fix (JENKINS-21486) not visible enough
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-34073 Plugin dependency fix (JENKINS-21486) not visible enough Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/06 10:14 PM Labels: 2.0 Priority: Critical Reporter: Daniel Beck This is about https://github.com/jenkinsci/jenkins/pull/2172 As I wrote in https://github.com/jenkinsci/jenkins/pull/2001, which is essentially its predecessor: I expect that this will result in a perceived regression in a large number of installations with broken configurations: While previously, only some (possibly unused) part of plugin functionality was unavailable due to class loading issues when that was actually used, now Jenkins will fail to load the entire plugin. Problems like the one described in the issue I expect to be a pretty rare and severe case of dependency problem. Therefore I have real concerns about this change without a corresponding change on the UI. I still have nightmares about 1.524, which fixed something similar. Of course, before PR 2172 even made it into a released version
[JIRA] [bitbucket-branch-source-plugin] (JENKINS-34072) Expose repository URL for consumption in Jenkinsfile
Title: Message Title Chris Pearce created an issue Jenkins / JENKINS-34072 Expose repository URL for consumption in Jenkinsfile Issue Type: New Feature Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Apr/06 9:56 PM Priority: Minor Reporter: Chris Pearce A common step as part of the Jenkinsfile pipeline definition is to retrieve the Git repository content. Exposing a parameter/variable (or something similar) would be helpful in avoiding the Jenkinsfile having hardcoded values. Add Comment
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Andrew Bayer commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Fwiw, the commit that removed it - groovy-core/commit/97d78e9e52deb52c8e66db501ef208f30384d014 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] [bitbucket-branch-source-plugin] (JENKINS-34071) Allow filtering by BitBucket Cloud projects
Title: Message Title Chris Pearce created an issue Jenkins / JENKINS-34071 Allow filtering by BitBucket Cloud projects Issue Type: New Feature Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Apr/06 9:28 PM Priority: Minor Reporter: Chris Pearce A common scenario is for repositories to be categorised/grouped using the new projects feature in BitBucket Cloud. It would be very useful for the folder computation to be able to filter the repositories to only include those that are assigned to a specific BitBucket Cloud project Add Comment
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Andrew Bayer commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Possibly relevant? https://github.com/gperfutils/gprof/commit/a579c5f165ab76ed3dd1aabdefa4611e8154a4ae 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] [workflow-plugin] (JENKINS-34070) Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing
Title: Message Title Jesse Glick commented on JENKINS-34070 Re: Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing Presumably a regression from the move from DescribableHelper to DescribableModel. 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] [workflow-plugin] (JENKINS-34070) Pipeline 2.0 causes snippet generator to throw exception when dealing with enums
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34070 Pipeline 2.0 causes snippet generator to throw exception when dealing with enums Change By: Jesse Glick Summary: Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing dealing with enums 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] [workflow-plugin] (JENKINS-34070) Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34070 Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing Change By: Jesse Glick Labels: regression 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] [workflow-plugin] (JENKINS-34070) Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34070 Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing Change By: Jesse Glick Priority: Minor Critical 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] [workflow-plugin] (JENKINS-34070) Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing
Title: Message Title Martin d'Anjou created an issue Jenkins / JENKINS-34070 Pipeline 2.0 causes snippet generator to throw exception when DataBoundConstructor is missing Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/06 8:56 PM Environment: Jenkins 1.642.3, Pipeline 2.0, Git Plugin 2.4.4, Git Client Plugin 1.19.6 Priority: Minor Reporter: Martin d'Anjou Using Jenkins 1.642.3 and Pipeline 2.0, an exception is thrown when the DataBoundConstructor is missing from plugin code. The problem can be reproduced with the following line up: Jenkins 1.642.3, Pipeline 2.0, Git Plugin 2.4.4, Git Client Plugin 1.19.6. The problem did not exists with Pipeline 1.15 and Jenkins 1.642.1. To reproduce the problem, install those plugins, create a Pipeline job, and go in the snippet generator, then: select the "checkout" step select Git
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Not hard to fix the error, and thus make most scripts work again. But SerializationTest.eachClosure still fails—meaning the patching is not effective in Groovy 2. 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] [delivery-pipeline-plugin] (JENKINS-34069) Aggregated view - Permanent Buils are not showing on Delivery Pipeline
Title: Message Title Cristiano Fontes created an issue Jenkins / JENKINS-34069 Aggregated view - Permanent Buils are not showing on Delivery Pipeline Issue Type: Bug Assignee: Patrik Boström Attachments: 2016-04-06 17_24_18-Skyline Delivery [Jenkins].png Components: delivery-pipeline-plugin Created: 2016/Apr/06 8:27 PM Priority: Minor Reporter: Cristiano Fontes I have a pipeline with Dev -> QA -> PROD What is happening is, it takes so long for builds to reach PRD that they reach the limit of 19 builds and are removed from view and also from the aggregated pipeline. Even the ones marked as permanent. This is really misleading, because there is a version deployed there, but the aggregated leads you to think there is none. Here is an example
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Andrew Bayer commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Do we have a full stacktrace for that? 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] [extensible-choice-parameter-plugin] (JENKINS-34068) Configuration Load does not pick up changes to Extensible-choice-parameter-plugin
Title: Message Title Jeff Miller created an issue Jenkins / JENKINS-34068 Configuration Load does not pick up changes to Extensible-choice-parameter-plugin Issue Type: Bug Assignee: Unassigned Components: extensible-choice-parameter-plugin Created: 2016/Apr/06 8:19 PM Environment: 1.642.3 Labels: config reload Priority: Minor Reporter: Jeff Miller Edit jp.ikedam.jenkins.plugins.extensible_choice_parameter.GlobalTextareaChoiceListProvider.xml to add in additional choices. Issue a configuration reload on the Jenkins server. When the Jenkins server is available again, the configuration does not show the edits for the new choices.
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade java.lang.ClassNotFoundException: org.codehaus.groovy.reflection.ClassInfo$ClassInfoSet 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] [kubernetes-plugin] (JENKINS-34067) kubernetes exception from "Test Connection" button
Title: Message Title Joshua Hoblitt commented on JENKINS-34067 Re: kubernetes exception from "Test Connection" button It looks like blanking out the CA cert textbox resolves the error. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Confirmed, bisecting with Jenkins 2 against groovy-cps versions points to this commit. 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] [kubernetes-plugin] (JENKINS-34067) kubernetes exception from "Test Connection" button
Title: Message Title Joshua Hoblitt updated an issue Jenkins / JENKINS-34067 kubernetes exception from "Test Connection" button Change By: Joshua Hoblitt Summary: kubernetes exception from "Test Connection" button 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] [kubernetes-plugin] (JENKINS-34067) exception from "Test Connection" button
Title: Message Title Joshua Hoblitt created an issue Jenkins / JENKINS-34067 exception from "Test Connection" button Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Apr/06 8:03 PM Environment: jenkins 1.651 kubernetes 0.5 Priority: Major Reporter: Joshua Hoblitt This stracetrace is displaced in the configuration dialog when attempt to test with valid credentials. Enabling/disabled tls cert validation seems to have no effect javax.servlet.ServletException: java.lang.StringIndexOutOfBoundsException: String index out of range: 1155 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) ...
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick commented on JENKINS-34064 Re: Pipeline builds do not run after Groovy 2.x upgrade Seems like the fix of JENKINS-26481 is incompatible with Groovy 2.x Kohsuke Kawaguchi. A hotfix would be to just disable that patch when 2.x is detected, but I would like to fix it to work in either. 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] [xvfb-plugin] (JENKINS-34066) Xvfb plugin is passing in -fbdir twice
Title: Message Title M Chon created an issue Jenkins / JENKINS-34066 Xvfb plugin is passing in -fbdir twice Issue Type: Bug Assignee: zregvart Attachments: xvfb fbdir flag.png Components: xvfb-plugin Created: 2016/Apr/06 7:52 PM Environment: Ubuntu 14.04 Priority: Minor Reporter: M Chon We were getting the following intermittent error on our builds: FATAL: /var/lib/jenkins/xvfb-157-8380869945976165128.fbdir/.nfs000ad5a20004f107: Device or resource busy java.nio.file.FileSystemException: /var/lib/jenkins/xvfb-157-8380869945976165128.fbdir/.nfs000ad5a20004f107: Device or resource busy at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) In order to address this, I started passing the following flag: "-fbdir /tmp" See attached screen shot. The error seems to have gone away, but in the console log, I see that the -fbdir flag is being passed twice. Does Xvfb ignore the first -fbdir parameter
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34064 Pipeline builds do not run after Groovy 2.x upgrade Change By: Jesse Glick Labels: 2.0 groovy regression 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] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Jesse Glick commented on JENKINS-34064 Re: Pipeline builds hang before starting any step Reproducible with mvn -f workflow-cps-plugin -Dtest=WorkflowTest\#demo surefire:test -Djenkins.version=… git bisect points to this commit updating Groovy from 1.x to 2.x. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds do not run after Groovy 2.x upgrade
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34064 Pipeline builds do not run after Groovy 2.x upgrade Change By: Jesse Glick Summary: Pipeline builds hang before starting any step do not run after Groovy 2.x upgrade 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] [core] (JENKINS-34065) Pinned label in plugin list
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-34065 Pinned label in plugin list Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/06 6:47 PM Labels: 2.0 Priority: Minor Reporter: Jesse Glick Run 2.0-beta-2. From /systemInfo you will see a Pinned column, which is now meaningless—always false. Should be deleted. Add Comment
[JIRA] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-34064 Pipeline builds hang before starting any step Change By: Antonio Muñiz Steps to reproduce it:# Install Jenkins 2.0-beta-2.# Restart# Upgrade Pipeline from 1.15 to 2.0 (in my case 2.0 was not propagated to my nearest UC [mirror|http://mirrors.clinkerhq.com/jenkins/updates/current/update-center.json] so the install wizard installed 1.15. I manually changed it to: http://ftp.icm.edu.pl/packages/jenkins/updates/current/update-center.json which already contains 2.0 packages). Make sure you mark all Pipeline related plugins (the ones that were aggregated by workflow-aggregator before 2.0) in the Upgrade tab (otherwise you will stay in 1.15 and only the aggregator is updated).# Create a pipeline with the script generated by the sample "Hello World".# Build it.# It hangs before starting any step and the CPS VM thread dump is empty. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-34064 Pipeline builds hang before starting any step Change By: Antonio Muñiz Environment: OSXJDK 8Jenkins 2.0-beta- 1 2 (suggested plugins)Pipeline 2.0 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] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Jesse Glick started work on JENKINS-34064 Change By: Jesse Glick 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] [git-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed
Title: Message Title Bobby Tait commented on JENKINS-32712 Re: Job with Git polling "succeeds" with "no changes" although the Git polling failed We've just discovered this issue too, and we typically use Jenkins as a fire-and-forget build tool until we're notified that a problem has occurred. Someone noticed we hadn't received any scheduled builds in a couple of days, despite new code pushes. For us, having some external notification telling us there was a problem with Jenkins that we need to check out immediately would be ideal. Something like an email or build failure (which would also send an email) or something else I'm not thinking of at the moment. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-34064 Pipeline builds hang before starting any step Change By: Antonio Muñiz Environment: OSXJDK 8Jenkins 2.0-beta- 2 1 (suggested plugins) Pipeline 2.0 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] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-34064 Pipeline builds hang before starting any step Change By: Antonio Muñiz Steps to reproduce it:# Install Jenkins 2.0-beta-2.# Upgrade Pipeline from 1.15 to 2.0 (in my case 2.0 was not propagated to my nearest UC [mirror|http://mirrors.clinkerhq.com/jenkins/updates/current/update-center.json] so the install wizard installed 1.15. I manually changed it to: http://ftp.icm.edu.pl/packages/jenkins/updates/current/update-center.json which already contains 2.0 packages). Make sure you mark all Pipeline related plugins (the ones that were aggregated by workflow-aggregator before 2.0) in the Upgrade tab (otherwise you will stay in 1.15 and only the aggregator is updated). # Create a pipeline with the script generated by the sample "Hello World".# Build it.# It hangs before starting any step and the CPS VM thread dump is empty. 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] [workflow-plugin] (JENKINS-34064) Pipeline builds hang before starting any step
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-34064 Pipeline builds hang before starting any step Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/06 6:20 PM Environment: OSX JDK 8 Jenkins 2.0-beta-2 Pipeline 2.0 Priority: Blocker Reporter: Antonio Muñiz Steps to reproduce it: Install Jenkins 2.0-beta-2. Upgrade Pipeline from 1.15 to 2.0 (in my case 2.0 was not propagated to my nearest UC mirror so the install wizard installed 1.15. I manually changed it to: http://ftp.icm.edu.pl/packages/jenkins/updates/current/update-center.json which already contains 2.0 packages). Create a pipeline with the script generated by the sample "Hello World". Build it.
[JIRA] [s3-plugin] (JENKINS-31119) S3 plugin should be compatible with the workflow plugin
Title: Message Title Jos Backus commented on JENKINS-31119 Re: S3 plugin should be compatible with the workflow plugin Thank you for this, and for the other improvements to the S3 plugin. Much appreciated, as it's allowed us to simplify our pipelines. 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] [cli] (JENKINS-33942) jenkins-cli.jar: set-build-description command fails with NPE for non-existent build
Title: Message Title dogfood commented on JENKINS-33942 Re: jenkins-cli.jar: set-build-description command fails with NPE for non-existent build Integrated in jenkins_main_trunk #4549 JENKINS-33942 Fixed NPE when non-exists run requested (Revision 575c1af489a43a6bc1846ca46864e5d4931e47e3) Result = SUCCESS pjanouse : 575c1af489a43a6bc1846ca46864e5d4931e47e3 Files : core/src/main/java/hudson/cli/SetBuildDescriptionCommand.java 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] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title Matthew Mitchell commented on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. Alright, I was unable to get an exact repo, but I think I saw enough, plus combined with the logs, to figure out what happens: 1) The PingFailureAnalyzer call in onDead in ChannelPinger.java will occasionally fail for various reasons. NPE's, findClass failures. Not always, but sometimes. When this happens, the master will NOT call close on the channel. 2) Normally this appears to be fine. The channel is somehow replaced or null'd out through other means. I think in cases of process termination or other semi-orderly shutdowns the socket connection is notified. 3) However, let's say there is a network anomoly. Power outage, network cable unplugged, dropped connection not on the server/client side. In this case, the master will notice, potentially by noticing a failed ping. If it fails in the PingFailureAnalyzer code, it won't close the channel. 4) The slave comes back, say from a reboot, or the network cable is reinstalled, etc. and attempts to reconnect. The channel is not null, and we get the error. I think the keys to the repro are the lack of a "Terminate" text in the slave log and the definite issue of not closing the channel when an exception is seen in the PFA. The lack of terminate indicates there was not an orderly shutdown of the channel on the client side. So, the fix would be to wrap the call to the PFA in a try catch to ensure that channel.close() is in fact called. The issues I was seeing in my installation have subsided, but this fix was made as they were tailing off, and I think I did not see any already connected errors after that. 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
[JIRA] [branch-api-plugin] (JENKINS-33808) Prove that richer Create Item API works by implementing for GH Org folders.
Title: Message Title Daniel Beck resolved as Done Jenkins / JENKINS-33808 Prove that richer Create Item API works by implementing for GH Org folders. Change By: Daniel Beck Status: In Progress Resolved Resolution: Done 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] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Title: Message Title Phil Johnson commented on JENKINS-26312 Re: Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Is this issue "really" fixed? We are experiencing the same exact issue (the footer overlaps the page buttons at the bottom if the SCM Sync Plugin is installed and checked the "Display Sync Status" checkbox for that plugin). Jenkins Version: Jenkins 1.642 SCM Sync (configuration) Plugin: 0.0.9 The issue seems to be that whenever there is a sync error the footer "grows". Any insight from those who have experienced this would be greatly appreciated. Cheers. 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] [dockerhub-notification-plugin] (JENKINS-34063) java.lang.ClassCastException in DockerHubTrigger Plugin
Title: Message Title Andrew Melo created an issue Jenkins / JENKINS-34063 java.lang.ClassCastException in DockerHubTrigger Plugin Issue Type: Bug Assignee: Unassigned Components: dockerhub-notification-plugin Created: 2016/Apr/06 5:32 PM Environment: Jenkins 2.0-beta1 from dockerhub Labels: docker Priority: Minor Reporter: Andrew Melo Trying to enable the "trigger on docker hub updates" box in a multibranchproject yields: javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject cannot be cast to hudson.model.Job at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [cli] (JENKINS-33942) jenkins-cli.jar: set-build-description command fails with NPE for non-existent build
Title: Message Title Paul Sokolovsky commented on JENKINS-33942 Re: jenkins-cli.jar: set-build-description command fails with NPE for non-existent build Thanks for quick turnaround! 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] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly
Title: Message Title James Nord commented on JENKINS-33926 Re: Jenkins no longer appears to shutdown correctly While investigating, I didn't see any error show up consistently before missing the log statement. I didn't see this occur as often on 2.0 before clicking the "Install New Features". Luckily it doesn't seem to be disruptive to my Jenkins, so that's a plus. Seems to imply it is reproduceable from the command line? Anyway I can reproduce it so you can always assign it to me 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] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title dogfood commented on JENKINS-21486 Re: Fail a plugin if its dependencies doesn't exist Integrated in jenkins_main_trunk #4548 JENKINS-21486 Follow-up (Revision 5ebf6b8bde83543a10dc21ef0dfd74872f20421e) Result = SUCCESS vincent latombe : 5ebf6b8bde83543a10dc21ef0dfd74872f20421e Files : core/src/main/java/hudson/PluginWrapper.java 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] [git-plugin] (JENKINS-33956) Git Plugin allows removing the last repository entry on the config screen
Title: Message Title Daniel Beck assigned an issue to Mark Waite Looks like an issue with the Git Plugin. On 1.x, it simply has "Delete Repository" buttons that do the same. For comparison, Subversion Plugin removes that button when there's only one location, and Jenkins 2.0 handles this correctly. Jenkins / JENKINS-33956 Git Plugin allows removing the last repository entry on the config screen Change By: Daniel Beck Summary: Jenkins 2.0 - 'X' Git Plugin allows removing the last repository entry on required conf elements the config screen Component/s: git-plugin Component/s: core Assignee: Daniel Beck Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33956) Jenkins 2.0 - 'X' on required conf elements
Title: Message Title Daniel Beck started work on JENKINS-33956 Change By: Daniel Beck 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/java/jenkins/install/UpgradeWizard.java http://jenkins-ci.org/commit/jenkins/52cc5f858108674ee70f76dbff0151eac864fadd Log: Merge pull request #2223 from kzantow/ JENKINS-34035 -easy-skip-setup-wizard [FIXED JENKINS-34035] - honor jenkins.install.runSetupWizard=false Compare: https://github.com/jenkinsci/jenkins/compare/c403e88f4403...52cc5f858108 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Code changed in jenkins User: kzantow Path: core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/java/jenkins/install/UpgradeWizard.java http://jenkins-ci.org/commit/jenkins/82c9e03d5ca9d3ad237c11842fb83d9467bae6d3 Log: JENKINS-34035 - honor jenkins.install.runSetupWizard=false 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34035 2.0 needs a stable/supported way to disable the Getting Started wizard Change By: SCM/JIRA link daemon Status: In Progress Resolved 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] [p4-plugin] (JENKINS-34062) Error with ResMerger in xcodebuild
Title: Message Title R S created an issue Jenkins / JENKINS-34062 Error with ResMerger in xcodebuild Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Apr/06 4:42 PM Environment: P4 plugin 1.3.7; Jenkins 1.656; Xcode 7.2.1 Build version 7C1002 Labels: xcode p4 Priority: Major Reporter: R S Projects that contain .rsrc files are failing when using the P4 Plug-in (https://wiki.jenkins-ci.org/display/JENKINS/P4+Plugin). using the older Perforce plug-in (https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin) does not cause this issue: file //appResource.rsrc: ### /Applications/Xcode.app/Contents/Developer/usr/bin/ResMerger - ERROR: eofErr Command /Applications/Xcode.app/Contents/Developer/usr/bin/ResMerger failed with exit code 1
[JIRA] [cli] (JENKINS-33942) jenkins-cli.jar: set-build-description command fails with NPE for non-existent build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33942 Re: jenkins-cli.jar: set-build-description command fails with NPE for non-existent build Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/cli/SetBuildDescriptionCommand.java http://jenkins-ci.org/commit/jenkins/511ccf0c836651d1d825c062d7d42338438c735c Log: Merge pull request #2230 from pjanouse/ JENKINS-33942 [FIX JENKINS-33942] Fixed NPE when non-exists run requested Compare: https://github.com/jenkinsci/jenkins/compare/0846358bf627...511ccf0c8366 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] [cli] (JENKINS-33942) jenkins-cli.jar: set-build-description command fails with NPE for non-existent build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33942 Re: jenkins-cli.jar: set-build-description command fails with NPE for non-existent build Code changed in jenkins User: Ing. Pavel Janousek Path: core/src/main/java/hudson/cli/SetBuildDescriptionCommand.java http://jenkins-ci.org/commit/jenkins/575c1af489a43a6bc1846ca46864e5d4931e47e3 Log: JENKINS-33942 Fixed NPE when non-exists run requested 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] [cli] (JENKINS-33942) jenkins-cli.jar: set-build-description command fails with NPE for non-existent build
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33942 jenkins-cli.jar: set-build-description command fails with NPE for non-existent build Change By: SCM/JIRA link daemon Status: Open Resolved 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] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly
Title: Message Title Daniel Beck resolved as Cannot Reproduce Resolving as Cannot Reproduce for now. I'll add test cases to RC/LTS testing plans so we make sure to check this for the 2.0 RC. Jenkins / JENKINS-33926 Jenkins no longer appears to shutdown correctly Change By: Daniel Beck Status: In Progress Resolved Resolution: Cannot Reproduce 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] [core] (JENKINS-34061) create symbolic link to last build
Title: Message Title yan bi created an issue Jenkins / JENKINS-34061 create symbolic link to last build Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Apr/06 3:50 PM Priority: Major Reporter: yan bi Hi, the symbolic link to lastStable and lastSuccessful work fine. But is it possible to implement also lastBuild symbolic link. Add Comment This message was sent by Atlassian
[JIRA] [core] (JENKINS-34061) create symbolic link to last build
Title: Message Title yan bi updated an issue Jenkins / JENKINS-34061 create symbolic link to last build Change By: yan bi Hi, the symbolic link to lastStable and lastSuccessful work fine. But is it possible to implement also lastBuild symbolic link . ? 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] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Fail a plugin if its dependencies doesn't exist Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/hudson/PluginWrapper.java http://jenkins-ci.org/commit/jenkins/5ebf6b8bde83543a10dc21ef0dfd74872f20421e Log: JENKINS-21486 Follow-up Display of shortName of disabled plugin is enough. Fix copy-paste error in the message for disabled dependencies 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] [core] (JENKINS-21486) Fail a plugin if its dependencies doesn't exist
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Fail a plugin if its dependencies doesn't exist Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginWrapper.java http://jenkins-ci.org/commit/jenkins/0846358bf62730a00cfed412b9e8bc0dc7cc1f8a Log: Merge pull request #2228 from Vlatombe/ JENKINS-21486 -follow-up JENKINS-21486 Follow-up Compare: https://github.com/jenkinsci/jenkins/compare/2c9adc9965e2...0846358bf627 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] [job-dsl-plugin] (JENKINS-34060) Unstable a build when DSL scripts pattern doesn't list any files
Title: Message Title Micah Zoltu commented on JENKINS-34060 Re: Unstable a build when DSL scripts pattern doesn't list any files This solution (marking builds as unstable) won't resolve my issue with JENKINS-30541 because it will result in every build being marked as unstable. I need a way to switch the validation to only require that DSL files were found it at least one folder. It is unclear to me why there is a desire to validate that every folder has a DSL file in it, I can't think of a situation where you have multiple glob patterns and every one must have a file in it. It seems to me that if you are using multiple globs the most likely scenario is that you are searching for a DSL rather than specifically loading each DSL. That being said, I would be fine with a checkbox to enable/disable this, or switch between "validate that at least one DSL was found" and "validate that all globs resulted in a DSL being found". 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] [core] (JENKINS-28521) Poll SCM
Title: Message Title
Himanshu Gaur commented on JENKINS-28521
Re: Poll SCM
Stack trace javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {"scmpoll_spec":"*/5","ignorePostCommitHooks":false}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33841) Support for pipeline builds
Title: Message Title Thomas VIAL commented on JENKINS-33841 Re: Support for pipeline builds I agree, we're deploying Jenkins2 using pipeline and SCM Jenkinsfile from Bitbucket and we'd like to get the build status in Bitbucket. Currently, the Stage View visualization only displays stages status, but no information regarding the branch name is provided. Also, bitbucket remains the place where code review is being done so having the build status is mandatory for reviewers. Thank you. 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-pipeline-plugin] (JENKINS-33895) build-pipeline-plugin does not support the pipeline (workflow) jobs
Title: Message Title Thomas VIAL updated an issue Jenkins / JENKINS-33895 build-pipeline-plugin does not support the pipeline (workflow) jobs Change By: Thomas VIAL Comment: I agree, we're deploying Jenkins2 using pipeline and SCM Jenkinsfile from Bitbucket and we'd like to get the build status in Bitbucket.Currently, the Stage View visualization only displays stages status, but no information regarding the branch name is provided.*Also, bitbucket remains the place where code review is being done so having the build status is mandatory for reviewers.*Thank you. 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-pipeline-plugin] (JENKINS-33895) build-pipeline-plugin does not support the pipeline (workflow) jobs
Title: Message Title Thomas VIAL commented on JENKINS-33895 Re: build-pipeline-plugin does not support the pipeline (workflow) jobs I agree, we're deploying Jenkins2 using pipeline and SCM Jenkinsfile from Bitbucket and we'd like to get the build status in Bitbucket. Currently, the Stage View visualization only displays stages status, but no information regarding the branch name is provided. Also, bitbucket remains the place where code review is being done so having the build status is mandatory for reviewers. Thank you. 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] [branch-api-plugin] (JENKINS-33808) Prove that richer Create Item API works by implementing for GH Org folders.
Title: Message Title Spike Washburn commented on JENKINS-33808 Re: Prove that richer Create Item API works by implementing for GH Org folders. Based on discussion with Manuel Jesús Recena Soto Jesse Glick and Daniel Beck, the work by manuel in https://github.com/jenkinsci/jenkins/pull/2117 has sufficiently proven that this API is rich enough to support more complicated scenarios. 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] [job-dsl-plugin] (JENKINS-34060) Unstable a build when DSL scripts pattern doesn't list any files
Title: Message Title Victor Martinez commented on JENKINS-34060 Re: Unstable a build when DSL scripts pattern doesn't list any files Initial approach: https://github.com/v1v/job-dsl-plugin/commit/82ef6729855eff4c28c0f8e747193e74f8bb03ff 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.
