[JIRA] [mailer-plugin] (JENKINS-34324) Fix PCT scenario against 2.0-rc
Title: Message Title Andres Rodriguez resolved as Fixed Jenkins / JENKINS-34324 Fix PCT scenario against 2.0-rc Change By: Andres Rodriguez 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] [golang-plugin] (JENKINS-34345) Add pipeline support
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-34345 Add pipeline support Issue Type: Improvement Assignee: Christopher Orr Components: golang-plugin Created: 2016/Apr/20 6:58 AM Priority: Major Reporter: Christopher Orr 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
[JIRA] [mailer-plugin] (JENKINS-32301) Jenkins mailer plugin breaks with two or more emails set in "Reply-To Address"
Title: Message Title Andres Rodriguez commented on JENKINS-32301 Re: Jenkins mailer plugin breaks with two or more emails set in "Reply-To Address" Released as 1.17 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] [mailer-plugin] (JENKINS-32301) Jenkins mailer plugin breaks with two or more emails set in "Reply-To Address"
Title: Message Title Andres Rodriguez closed an issue as Fixed Jenkins / JENKINS-32301 Jenkins mailer plugin breaks with two or more emails set in "Reply-To Address" Change By: Andres Rodriguez Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-34152) Attempting to unlock emulator screen FATAL: null java.lang.NullPointerException
Title: Message Title Christopher Orr commented on JENKINS-34152 Re: Attempting to unlock emulator screen FATAL: null java.lang.NullPointerException Anton Averin: There haven't been any updates here, or in the Jenkins plugin manager, or on the wiki page for this plugin, meaning that a release has not yet been made. 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-34344) Slave is not disconnected once it is terminted. Error: channel is already closed
Title: Message Title sumit gerela created an issue Jenkins / JENKINS-34344 Slave is not disconnected once it is terminted. Error: channel is already closed Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, swarm-plugin Created: 2016/Apr/20 6:49 AM Environment: Jenkins ver. 1.625.2, Jenkins Swarm Version Plugin Version: 1.26 Priority: Critical Reporter: sumit gerela javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-1.625.2.jar!/hudson/slaves/SlaveComputer/systemInfo.jelly:52:65: channel is already closed at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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:8
[JIRA] [android-emulator-plugin] (JENKINS-34152) Attempting to unlock emulator screen FATAL: null java.lang.NullPointerException
Title: Message Title Anton Averin commented on JENKINS-34152 Re: Attempting to unlock emulator screen FATAL: null java.lang.NullPointerException Was this fix already released or we still need to grab hpi manually? 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] [packaging] (JENKINS-30999) Jenkins installer not starting after finishing the installation on OS X El Capitan
Title: Message Title sumit gerela closed an issue as Fixed Jenkins / JENKINS-30999 Jenkins installer not starting after finishing the installation on OS X El Capitan Change By: sumit gerela Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21486) Refuse to load a plugin if dependencies are disabled or outdated
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Refuse to load a plugin if dependencies are disabled or outdated Code changed in jenkins User: Kohsuke Kawaguchi 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/b396deda7fd6b70557710df275d54d35d8f23cb5 Log: Merge pull request #2278 from daniel-beck/1.x-JENKINS-34073 Revert "[FIXED JENKINS-21486] Merged #2172: enforce plugin dependenci… Compare: https://github.com/jenkinsci/jenkins/compare/c51c7dcee272...b396deda7fd6 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) Refuse to load a plugin if dependencies are disabled or outdated
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-21486 Refuse to load a plugin if dependencies are disabled or outdated 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] [core] (JENKINS-21486) Refuse to load a plugin if dependencies are disabled or outdated
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21486 Re: Refuse to load a plugin if dependencies are disabled or outdated 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/e0828dd7c85f0b0e874823dad625ebb0a6a17cd5 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] [parameterized-remote-trigger-plugin] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Adrian Popa commented on JENKINS-32462 Re: Checking Status of remote job fail IT works just fine with multiple parameters for me. I print the message in Job B in the console and exit with that exit 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] [parameterized-remote-trigger-plugin] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Chinmayee Nagaraju commented on JENKINS-32462 Re: Checking Status of remote job fail Thanks ! it works when there is only 1 parameter - uniqueMarker on the remote job .. when there are multiple other parameters.. it still is checking for the older builds 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] [parameterized-remote-trigger-plugin] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Adrian Popa edited a comment on JENKINS-32462 Re: Checking Status of remote job fail [~chinmayeevasisht]Job A on Jenkins A triggers a job B on Jenkins B.In job A's config page, go to Trigger a remote parameterized job (the plugin) / Job Info / Parameters and write "uniqueMarker=$BUILD_NUMBER", without the quotes.In Job B's config check "This is a parameterized build" and add a string parameter called uniqueMarker.That's it :) The remote trigger plugin seems to identify the build you just triggered by the parameters it has been started with, and not by the build number. I guess this is because the build (of job B) doesn't get a build number until it exits the queue. You can use any parameter name with any unique value, something like the current time would also work.!http:// i. imgur.com/xhb57Eg .png ! 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] [parameterized-remote-trigger-plugin] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Adrian Popa edited a comment on JENKINS-32462 Re: Checking Status of remote job fail [~chinmayeevasisht]Job A on Jenkins A triggers a job B on Jenkins B.In job A's config page, go to Trigger a remote parameterized job (the plugin) / Job Info / Parameters and write "uniqueMarker=$BUILD_NUMBER", without the quotes.In Job B's config check "This is a parameterized build" and add a string parameter called uniqueMarker.That's it :) The remote trigger plugin seems to identify the build you just triggered by the parameters it has been started with, and not by the build number. I guess this is because the build (of job B) doesn't get a build number until it exits the queue. You can use any parameter name with any unique value, something like the current time would also work. !http://imgur.com/xhb57Eg! 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] [jacoco-plugin] (JENKINS-34343) PMD, Jacococ code coverage report and Junit report send in mail
Title: Message Title sunil garje created an issue Jenkins / JENKINS-34343 PMD, Jacococ code coverage report and Junit report send in mail Issue Type: Task Assignee: Ognjen Bubalo Components: jacoco-plugin, junit-plugin, mailer-plugin, pmd-plugin Created: 2016/Apr/20 5:45 AM Environment: Development Priority: Major Reporter: sunil garje Hi Team, In my Dev environment in Jenkins while building project PMD, Jacococ code coverage report and Junit report gets generated so we have new requirment like these reports snapshots should get attached and send via mail to developers automatically through Jenkins so can you please tell me is it possible? if yes then please tell me steps to achieve it. Thanks & Regards, Sunil Garje
[JIRA] [core] (JENKINS-34281) Queue isn't saved on any shutdown
Title: Message Title Daniel Beck commented on JENKINS-34281 Re: Queue isn't saved on any shutdown Sam Van Oort Could you please determine whether this is a recent change? Which Jenkins 1.x fail to save the queue in this situation? Some ideas: 1.653/PR 2103; 1.638/SECURITY-186. 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] [parameterized-remote-trigger-plugin] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Adrian Popa commented on JENKINS-32462 Re: Checking Status of remote job fail Chinmayee Nagaraju Job A on Jenkins A triggers a job B on Jenkins B. In job A's config page, go to Trigger a remote parameterized job (the plugin) / Job Info / Parameters and write "uniqueMarker=$BUILD_NUMBER", without the quotes. In Job B's config check "This is a parameterized build" and add a string parameter called uniqueMarker. That's it The remote trigger plugin seems to identify the build you just triggered by the parameters it has been started with, and not by the build number. I guess this is because the build (of job B) doesn't get a build number until it exits the queue. You can use any parameter name with any unique value, something like the current time would also work. 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-34342) Remove version from X-Hudson and X-Jenkins headers
Title: Message Title
Owen Wood updated an issue
Jenkins / JENKINS-34342
Remove version from X-Hudson and X-Jenkins headers
Change By:
Owen Wood
Jenkins version information is available via these headers.{code}$ curl --head http://localhost:8080/HTTP/1.1 200 OKX-Content-Type-Options: nosniffCache-Control: no-cache,no-store,must-revalidateX-Hudson-Theme: defaultContent-Type: text/html;charset=UTF-8Set-Cookie: JSESSIONID.e1a19b4b=1gfm5fw8eis821xv28jzelg745;Path=/;HttpOnlyExpires: Thu, 01 Jan 1970 00:00:00 GMTX-Hudson: 1.395X-Jenkins: 1.625X-Jenkins-Session: 786ba6b1X-Frame-Options: sameoriginX-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhbOS0Es16jqr0KkNm8mqCHqs0rgTjvpA/gKkPE5Nii0xr6Z0TL08EEGdtns+Tufwk3kSb1fFH/+H1CxEJya2H4gwNcklRt5iB4f1Sfxt9HZ5/MkvCwpuGcVbsJqQaTYWVb7e2/Hcf1+Zh+zDpQCTJ8L5QrttoT80CMypF9Jo4JklUbi1lGjxSY2duN++0Gl10+jAmmouy0KqmeYM4HD/uUS+C2aM0Dlma1X/vSsIcjMeF70YKeA1FuI45uEqsfJSe1+rPknoCC6F2C3ZqcyhSnVP5Vh+5ijdNx1cvkb9JWiY6cmt9IWPI2sBpZB3qOwBrc2ty81anerf8kCFrW3ALQIDAQABContent-Length: 11381Server: Jetty(winstone-2.8){code} {{X-Hudson}} usages in jenkins:* https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/Main.java#L100* https://github.com/jenkinsci/jenkins/blob/9fce1ee933eb5276baff977d562fc8e183f1c8d6/core/src/main/java/hudson/util/FormFieldValidator.java#L337* https://github.com/jenkinsci/jenkins/blob/master/cli/src/main/java/hudson/cli/CLI.java#L281{{X-Jenkins}} usage in jenkins:* https://github.com/jenkinsci/jenkins/blob/master/cli/src/main/java/hudson/cli/CLI.java#L281
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34342) Remove version from X-Hudson and X-Jenkins headers
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-34342 Remove version from X-Hudson and X-Jenkins headers Issue Type: Improvement Assignee: Unassigned Components: core, security Created: 2016/Apr/20 5:36 AM Priority: Major Reporter: Owen Wood Jenkins version information is available via these headers. $ curl --head http://localhost:8080/ HTTP/1.1 200 OK X-Content-Type-Options: nosniff Cache-Control: no-cache,no-store,must-revalidate X-Hudson-Theme: default Content-Type: text/html;charset=UTF-8 Set-Cookie: JSESSIONID.e1a19b4b=1gfm5fw8eis821xv28jzelg745;Path=/;HttpOnly Expires: Thu, 01 Jan 1970 00:00:00 GMT X-Hudson: 1.395 X-Jenkins: 1.625 X-Jenkins-Session: 786ba6b1 X-Frame-Options: sameorigin X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhbOS0Es16jqr0KkNm8mqCHqs0rgTjvpA/gKkPE5Nii0xr6Z0TL08EEGdtns+Tufwk3kSb1fFH/+H1CxEJya2H4gwNcklRt5iB4f1Sfxt9HZ5/MkvCwpuGcVbsJqQaTYWVb7e2/Hcf1+Zh+zDpQCTJ8L5QrttoT80CMypF9Jo4JklUbi1lGjxSY2duN++0Gl10+jAmmouy0KqmeYM4HD/uUS+C2aM0Dlma1X/vSsIcjMeF70YKeA1FuI45uEqsfJSe1+rPknoCC6F2C3ZqcyhSnVP5Vh+5ijdNx1cvkb9JWiY6cmt9IWPI2sBpZB3qOwBrc2ty81anerf8kCFrW3ALQIDAQAB Content-Length: 11381 Server: Jetty(winstone-2.8)
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-32462) Checking Status of remote job fail
Title: Message Title Chinmayee Nagaraju commented on JENKINS-32462 Re: Checking Status of remote job fail Adrian Pop How do you use this uniqueMarker=$BUILD_NUMBER ? I still see this when i provide uniqueMarker Triggering remote job now. Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build. Checking parameters of #25 Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build. Query failed. Checking parameters of #24 Unable to find expected value for Environment Unable to find expected value for platform Unable to find expected value for testsuit Unable to find expected value for summarypath Unable to find expected value for createbugonfailure Unable to find expected value for cyclename Unable to find expected value for fuzenodeLoc Unable to find expected value for fullyQaulifiedDomainName Param uniqueMarker doesn't match! Checking parameters of #26 Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build. Query failed. Checking parameters of #23 Unable to find expected value for Environment Unable to find expected value for platform Unable to find expected value for testsuit Unable to find expected value for summarypath Unable to find expected value for createbugonfailure Unable to find expected value for cyclename Unable to find expected value for fuzenodeLoc Unable to find expected value for fullyQaulifiedDomainName This job is build #[23] on the remote server. 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-25638) Cannot prevent concurrent build pipelines
Title: Message Title
Bruce Fraser edited a comment on JENKINS-25638
Re: Cannot prevent concurrent build pipelines
We have been using the "Block build when downstream project is building" on all of our jobs for the last year. We have confirmed that even with this set it fails at least some of the time, in what I suspect is a race condition. What we see is that on some rare occasions, a second pipeline job will start just a second after one of the downstream jobs starts. The log below is crude, but shows the Process ID, date and time, Job Start and End, the workspace inherited from the upstream job and a database inherited from an upstream job. At 00:23:49 there was a downstream job started, then at 00:23:50 the concurrent job starts doing a git clean and obliterates files being used by the downstream job. Gerit2 and Master are both at the head of pipelines. All other jobs are downstream. {noformat}104 19/04/16 23:38:34 Start Gerit2 /home/jenkins/workspace/Gerrit25238 20/04/16 00:01:30 End Master /home/jenkins/workspace/Master/debug/no/simtime/yes debug=no simtime=yes5238 20/04/16 00:01:44 Start Master /home/jenkins/workspace/Master/debug/yes/simtime/yes debug=yes simtime=yes104 20/04/16 00:04:08 End Gerit2 /home/jenkins/workspace/Gerrit23028 20/04/16 00:04:19 Start Export /home/jenkins/workspace/Gerrit2 NZDEV25238 20/04/16 00:22:54 End Master /home/jenkins/workspace/Master/debug/yes/simtime/yes debug=yes simtime=yes3028 20/04/16 00:23:37 End Export /home/jenkins/workspace/Gerrit2 NZDEV22661 20/04/16 00:23:49 Start PBuild /home/jenkins/workspace/Gerrit2 NZDEV2105 20/04/16 00:23:50 Start Gerit2 /home/jenkins/workspace/Gerrit23029 20/04/16 00:23:52 Start Export /home/jenkins/workspace/Master/debug/no/simtime/no NZDEV25239 20/04/16 00:24:08 Start Master /home/jenkins/workspace/Master/debug/no/simtime/no debug=no simtime=no3029 20/04/16 00:25:18 End Export /home/jenkins/workspace/Master/debug/no/simtime/no NZOK105 20/04/16 00:50:23 End Gerit2 /home/jenkins/workspace/Gerrit23030 20/04/16 00:50:34 Start Export /home/jenkins/workspace/Gerrit2 NZDEV25239 20/04/16 00:50:46 End Master /home/jenkins/workspace/Master/debug/no/simtime/no debug=no simtime=no5239 20/04/16 00:51:08 Start Master /home/jenkins/workspace/Master/debug/yes/simtime/no debug=yes simtime=no{noformat}Jenkins and all plugins were upgraded to the latest just last week.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-pipeline-plugin] (JENKINS-25638) Cannot prevent concurrent build pipelines
Title: Message Title Bruce Fraser commented on JENKINS-25638 Re: Cannot prevent concurrent build pipelines We have been using the "Block build when downstream project is building" on all of our jobs for the last year. We have confirmed that even with this set it fails at least some of the time, in what I suspect is a race condition. What we see is that on some rare occasions, a second pipeline job will start just a second after one of the downstream jobs starts. The log below is crude, but shows the Process ID, date and time, Job Start and End, the workspace inherited from the upstream job and a database inherited from an upstream job. 104 19/04/16 23:38:34 Start Gerit2 /home/jenkins/workspace/Gerrit2 5238 20/04/16 00:01:30 End Master /home/jenkins/workspace/Master/debug/no/simtime/yes debug=no simtime=yes 5238 20/04/16 00:01:44 Start Master /home/jenkins/workspace/Master/debug/yes/simtime/yes debug=yes simtime=yes 104 20/04/16 00:04:08 End Gerit2 /home/jenkins/workspace/Gerrit2 3028 20/04/16 00:04:19 Start Export /home/jenkins/workspace/Gerrit2 NZDEV2 5238 20/04/16 00:22:54 End Master /home/jenkins/workspace/Master/debug/yes/simtime/yes debug=yes simtime=yes 3028 20/04/16 00:23:37 End Export /home/jenkins/workspace/Gerrit2 NZDEV2 2661 20/04/16 00:23:49 Start PBuild /home/jenkins/workspace/Gerrit2 NZDEV2 105 20/04/16 00:23:50 Start Gerit2 /home/jenkins/workspace/Gerrit2 3029 20/04/16 00:23:52 Start Export /home/jenkins/workspace/Master/debug/no/simtime/no NZDEV2 5239 20/04/16 00:24:08 Start Master /home/jenkins/workspace/Master/debug/no/simtime/no debug=no simtime=no 3029 20/04/16 00:25:18 End Export /home/jenkins/workspace/Master/debug/no/simtime/no NZOK 105 20/04/16 00:50:23 End Gerit2 /home/jenkins/workspace/Gerrit2 3030 20/04/16 00:50:34 Start Export /home/jenkins/workspace/Gerrit2 NZDEV2 5239 20/04/16 00:50:46 End Master /home/jenkins/workspace/Master/debug/no/simtime/no debug=no simtime=no 5239 20/04/16 00:51:08 Start Master /home/jenkins/workspace/Master/debug/yes/simtime/no debug=yes simtime=no Jenkins and all plugins were upgraded to the latest just last week. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-pipeline-plugin] (JENKINS-33935) Can't rerun a build
Title: Message Title
Daniel O'Connor commented on JENKINS-33935
Re: Can't rerun a build
Is this related to https://github.com/jenkinsci/build-pipeline-plugin/commit/d56ff03bf4838c541e68f4cfc06f59ba78d12317 -
final List causes = new ArrayList();
causes.add(new UserIdCause());
private void filterOutUserIdCause(CauseAction causeAction) {
final Iterator it = causeAction.getCauses().iterator();
while (it.hasNext()) {
final Cause cause = it.next();
if (cause instanceof UserIdCause) {
it.remove(); // This is now being triggered, where the previous release didn't see a UserIdCause
}
}
}
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-33935) Can't rerun a build
Title: Message Title
Daniel O'Connor updated an issue
Jenkins / JENKINS-33935
Can't rerun a build
Change By:
Daniel O'Connor
When I try to rerun a build from pipeline view which was already run, there is no new build job queued and I end up with the following log entries:Running build again: pipeline-test-3#1 {code} Mar 31, 2016 2:10:31 PM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCallcall to /$stapler/bound/3d13fec7-bc73-4725-8aff-7bf4774061bd/rerunBuild failedjava.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1069) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.filterOutUserIdCause(BuildPipelineView.java:628) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.filterActions(BuildPipelineView.java:603) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.rerunBuild(BuildPipelineView.java:422) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:474) 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.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) 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:199) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117
[JIRA] [extended-choice-parameter-plugin] (JENKINS-34199) Cannot use a simple Groovy Script
Title: Message Title vimil resolved as Cannot Reproduce I am marking this issue as cannot repro Jenkins / JENKINS-34199 Cannot use a simple Groovy Script Change By: vimil Status: Open 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] [golang-plugin] (JENKINS-32946) code.google.com downloads seem to have been migrated to github
Title: Message Title Christopher Orr closed an issue as Won't Fix Jenkins / JENKINS-32946 code.google.com downloads seem to have been migrated to github Change By: Christopher Orr Status: Open Closed Resolution: Won't Fix 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] [golang-plugin] (JENKINS-32946) code.google.com downloads seem to have been migrated to github
Title: Message Title Christopher Orr commented on JENKINS-32946 Re: code.google.com downloads seem to have been migrated to github GitHub Releases doesn't have the binaries, only zips of the source. A related ticket was recently resolved here: https://github.com/golang/go/issues/15284 From the PR linked there (https://golang.org/cl/22165), they just removed the broken code.google.com link from the Go website, and don't actually know where the old binaries are... Since the newest releases are still being picked up by the backend crawler, and nobody should really care about versions of Go older than 1.2, and because nobody has complained, I'm going to close this for now. 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-33151) GitHub commit status design is bad
Title: Message Title Nathan Loewen commented on JENKINS-33151 Re: GitHub commit status design is bad Jesse Glick The plugin you linked seems to be focused exclusively on pull requests and doesn't seem to enable these kind of workflows. Additionally, I have been unable to find any plugin which allows this functionality. I would find the functionality Arthur Schreiber described very helpful; in particular, the ability to set the context of the GitHub status. I suspect there are others who would as well. Is there any way this functionality could be reconsidered even in part? 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] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Christopher Orr commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds I just noticed the same problem with the (master branch of) Android Lint plugin, which is also based upon analysis-core. 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] [CocoaPods] (JENKINS-34341) Cocoapods Running through issues installing pods
Title: Message Title Sunil Gandham commented on JENKINS-34341 Re: Cocoapods Running through issues installing pods Leif Janzik Can you have a look this as it is blocking my work for last 2 days and I couldnt resolve the issue. 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 That's a different URL than I'm accustomed to using for the experimental update center. If you don't mind downloading it directly from artifactory (and then uploading it using the Advanced page of "Manage plugins"), you can get it at https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/2.5.0-beta5/git-2.5.0-beta5.hpi 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] [sauce-ondemand-plugin] (JENKINS-32728) NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)
Title: Message Title Gavin Mogan resolved as Incomplete Jenkins / JENKINS-32728 NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName) Change By: Gavin Mogan Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-32669) Launch Unity with different commandline arguments depending on environment variables/build parameters
Title: Message Title lacostej commented on JENKINS-32669 Re: Launch Unity with different commandline arguments depending on environment variables/build parameters Hello Manuel, I would try solving this with environment variables. Your build parameter points to a file containing the set of variables for your build, including your set of arguments. E.g. ARG=Env1 or Env2 then .env.Env1 contains UNITY_ARGS=A .env.Env2 contains UNITY_ARGS=B. load those using EnvInject or similar (https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin) configure the job to run with $UNITY_ARGS as arguments. 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 Ben Place commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated I've looked in http://mirror.xmission.com/jenkins/updates/experimental/update-center.json for git:2.5.0-beta5, but all I see is git:2.5.0-beta4. Is there some other place I can look for it? Do I just need to wait for it to propagate to other mirrors? 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] [unity3d-plugin] (JENKINS-32356) Workflow build step for Unity3D
Title: Message Title lacostej commented on JENKINS-32356 Re: Workflow build step for Unity3D Hello Scott. Is this something you want to help contributing ? It shouldn't be hard. I will be able to tackle this in some weeks, but haven't the need yet as my server isn't yet configured to use the workflows. 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] [unity3d-plugin] (JENKINS-34339) Unable to select Unity installation
Title: Message Title lacostej updated an issue Jenkins / JENKINS-34339 Unable to select Unity installation Change By: lacostej Attachment: Screen Shot 2016-04-19 at 19.26.06.png 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] [unity3d-plugin] (JENKINS-34339) Unable to select Unity installation
Title: Message Title lacostej commented on JENKINS-34339 Re: Unable to select Unity installation Hello, if you are using a master/slave setup, on your slave, you will have to configure things up: If this isn't your setup, please give more information. I have a Mac master and no issue at all. 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-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-18032 "Delete Project" link fails with 403 Exception: No valid crumb was included in the request Change By: Steven Christou Labels: 1.509.3-fixed 2.0-planned crumb 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort commented on JENKINS-34281 Re: Queue isn't saved on any shutdown Daniel Beck I have just confirmed that 1.x will fail to save queues where anonymous lacks read access, yes (when killed by Ctrl+C, of course). Surprised nobody has mentioned this issue yet... 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-34281) Queue isn't saved on any shutdown
Title: Message Title Daniel Beck commented on JENKINS-34281 Re: Queue isn't saved on any shutdown For confirmation, same queue non-saving behavior should occur on 1.x when using matrix security that grants no permissions to anon. Right? 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-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33809 Re: Find out what's wrong with the tests on the 2.0 branch requiring so much RAM Code changed in jenkins User: Daniel Beck Path: test/pom.xml http://jenkins-ci.org/commit/jenkins/0d0314ddee72b227a770d294549d12ded3b3fbac Log: JENKINS-33809 Don't reuse forks 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-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33809 Re: Find out what's wrong with the tests on the 2.0 branch requiring so much RAM Code changed in jenkins User: Daniel Beck Path: test/pom.xml http://jenkins-ci.org/commit/jenkins/574f83a962a62021cc60b6af1e3de5c0f1f008b8 Log: Merge pull request #2264 from daniel-beck/reuseForks=false JENKINS-33809 Don't reuse forks Compare: https://github.com/jenkinsci/jenkins/compare/4f51944cf1f9...574f83a962a6 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-34093) 2.0 introduces TopLevelItemDescriptor.LOGGER that is not private
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34093 Re: 2.0 introduces TopLevelItemDescriptor.LOGGER that is not private Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/TopLevelItemDescriptor.java http://jenkins-ci.org/commit/jenkins/b01a1b1c15b3ed17a5bb4d584218ef3e9cf3de3f Log: [FIX JENKINS-34093] Make logger field private 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-34093) 2.0 introduces TopLevelItemDescriptor.LOGGER that is not private
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34093 Re: 2.0 introduces TopLevelItemDescriptor.LOGGER that is not private Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/TopLevelItemDescriptor.java http://jenkins-ci.org/commit/jenkins/4f51944cf1f9fcf4d8b5bb4a9671730bf455838c Log: Merge pull request #2271 from daniel-beck/ JENKINS-34093 [FIX JENKINS-34093] Make logger field private Compare: https://github.com/jenkinsci/jenkins/compare/51b70aea3754...4f51944cf1f9 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-34093) 2.0 introduces TopLevelItemDescriptor.LOGGER that is not private
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34093 2.0 introduces TopLevelItemDescriptor.LOGGER that is not private 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] [core] (JENKINS-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-34281 Queue isn't saved on any shutdown Change By: Sam Van Oort URL: https://github.com/jenkinsci/jenkins/pull/2276 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] [exclusion-plugin] (JENKINS-12399) Dynamic exclusion resourced based on parameter name
Title: Message Title Anthony Roux resolved as Fixed Should be Fixed with the contribution of https://github.com/kool79 https://github.com/jenkinsci/exclusion-plugin/commit/ed36b786e03b9c53faf87440a24bbd6e33e92053 Reopen if not. Jenkins / JENKINS-12399 Dynamic exclusion resourced based on parameter name Change By: Anthony Roux Status: Open Resolved Assignee: Anthony Roux 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
[JIRA] [exclusion-plugin] (JENKINS-30877) Exclusion admin panel doesn't work right with dynamic resource names
Title: Message Title Anthony Roux resolved as Fixed Fixed with the contribution of https://github.com/kool79 https://github.com/jenkinsci/exclusion-plugin/commit/ed36b786e03b9c53faf87440a24bbd6e33e92053 Jenkins / JENKINS-30877 Exclusion admin panel doesn't work right with dynamic resource names Change By: Anthony Roux Status: Open Resolved Assignee: Anthony Roux 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 j
[JIRA] [exclusion-plugin] (JENKINS-23010) Exclusion-Plugin Control Panel doesn't update; doesn't report parameter values
Title: Message Title Anthony Roux resolved as Fixed Fixed with the contribution of https://github.com/kool79 https://github.com/jenkinsci/exclusion-plugin/commit/ed36b786e03b9c53faf87440a24bbd6e33e92053 Jenkins / JENKINS-23010 Exclusion-Plugin Control Panel doesn't update; doesn't report parameter values Change By: Anthony Roux 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] [exclusion-plugin] (JENKINS-23010) Exclusion-Plugin Control Panel doesn't update; doesn't report parameter values
Title: Message Title Anthony Roux assigned an issue to Anthony Roux Jenkins / JENKINS-23010 Exclusion-Plugin Control Panel doesn't update; doesn't report parameter values Change By: Anthony Roux Assignee: Anthony Roux 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort commented on JENKINS-34281 Re: Queue isn't saved on any shutdown So, to summarize: Too long; Didn't read summary: Jenkins wasn't running some forms of shutdown as the system user, and when we removed anonymous read access as part of the secure-out-of-the-box PR (https://github.com/jenkinsci/jenkins/pull/2042/files#diff-f65b8a70854ca1cc6c12397eee54d279R62) then it could no longer see build items to persist them. * Build queue was not persisted on shutdown, when doing a new Jenkins 2.0 install with setup wizard. The file was made, but no Items (builds) were included. Result: disappearing builds. Build queue was not persisted because when saving the queue, it lists the items to save with Queue queue.getItems(), which returned an empty list getItems() returns an empty list, because items are only returned when permissions make them readable, and during shutdown it did not have permissions to read them (permission check failed) During shutdown, read permissions were not present because secure-out-of-the-box removed anonymous read access that allowed it to work before. Solution: run shutdown correctly as system user, which has full permissions Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received thi
[JIRA] [core] (JENKINS-33852) Exception while copying in thread - causes Slave disconnection
Title: Message Title Noam Manos commented on JENKINS-33852 Re: Exception while copying in thread - causes Slave disconnection Many attempts to find cause in Maven configuration, or in Java implementation, or to set any known Jenkins configuration, to workaround this problem, did not succeed, and this unpredictable error kept on happening, until... I asked our IT guys to increase CPU and RAM (from 4GB to 16GB), and walla - the problem disappeared. It's still a bug, but at least now with a workaround. 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] [docker-workflow-plugin] (JENKINS-34289) docker.image.inside fails unexpectedly with Jenkinsfile
Title: Message Title Christian Höltje commented on JENKINS-34289 Re: docker.image.inside fails unexpectedly with Jenkinsfile If it helps, I was able to use auditd to see that execve() was called for the docker exec for the command in question and execve() returned 0 (which is not the exit code, but just says the syscall worked). So the command seems to be run by Jenkins. It just isn't getting the exit code back correctly (and gets -1 instead). Looking around, could this be related to JENKINS-25727 ? If I'm reading the code correctly, this is falling afoul of this code: https://github.com/jenkinsci/durable-task-plugin/blob/66d80d2b9761ebdb4f0d3bb7b9edb82357e33399/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java#L172-L174 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] [CocoaPods] (JENKINS-34341) Cocoapods Running through issues installing pods
Title: Message Title Sunil Gandham created an issue Jenkins / JENKINS-34341 Cocoapods Running through issues installing pods Issue Type: Bug Assignee: Leif Janzik Components: CocoaPods, cocoapods-integration Created: 2016/Apr/19 7:37 PM Priority: Minor Reporter: Sunil Gandham Command ``` /usr/local/bin/pod install ``` Report
[JIRA] [jira-trigger-plugin] (JENKINS-34301) Plugin swallows every exceptions thrown in http requests
Title: Message Title Wisen Tanasa resolved as Fixed Jenkins / JENKINS-34301 Plugin swallows every exceptions thrown in http requests Change By: Wisen Tanasa 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] [text-file-operations-plugin] (JENKINS-32694) NullPointerException at CreateTextFile.CreateFileTask.call()
Title: Message Title Noam Manos commented on JENKINS-32694 Re: NullPointerException at CreateTextFile.CreateFileTask.call() Yep, now working. Thank you, great plugin! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-trigger-plugin] (JENKINS-34301) Plugin swallows every exceptions thrown in http requests
Title: Message Title Wisen Tanasa commented on JENKINS-34301 Re: Plugin swallows every exceptions thrown in http requests Released under 0.2.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] [docker-workflow-plugin] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Radesh Rao commented on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
The test job that I had succeeds with the patch:
Started by user Radesh Rao
[Pipeline] Allocate node : Start
Running on docker in /data/jenkins/workspace/My pipeline
[Pipeline] node {
[Pipeline] Set environment variables : Start
[Pipeline] withEnv {
[Pipeline] Sets up Docker registry endpoint : Start
[Pipeline] withDockerRegistry {
[Pipeline] sh
[Cloud pipeline] Running shell script
+ echo my.registry.com/build-env:jdk8-maven3 -- build-env:jdk8-maven3
my.registry.com/build-env:jdk8-maven3 -- build-env:jdk8-maven3
[Pipeline] sh
[Cloud pipeline] Running shell script
+ docker inspect -f . build-env:jdk8-maven3
Error: No such image or container: build-env:jdk8-maven3
[Pipeline] sh
[Cloud pipeline] Running shell script
+ docker pull my.registry.com/build-env:jdk8-maven3
jdk8-maven3: Pulling from build-env
//
// snip
//
Status: Image is up to date for my.registry.com/build-env:jdk8-maven3
[Pipeline] Run build steps inside a Docker container : Start
$ docker run -t -d -u 995:991 -w "/data/jenkins/workspace/My pipeline" -v "/data/jenkins/workspace/My pipeline:/data/jenkins/workspace/My pipeline:rw" -v "/data/jenkins/workspace/My pipeline@tmp:/data/jenkins/workspace/My pipeline@tmp:rw" -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e my.registry.com/build-env:jdk8-maven3 cat
[Pipeline] withDockerContainer {
[Pipeline] sh
[Cloud pipeline] Running shell script
+ echo Hello
Hello
[Pipeline] } //withDockerContainer
$ docker stop a9bf6ced0bceb9731144db9d639ae702587238d67ad5af55107dec5e5ad54333
$ docker rm -f a9bf6ced0bceb9731144db9d639ae702587238d67ad5af55107dec5e5ad54333
[Pipeline] Run build steps inside a Docker container : End
[Pipeline] } //withDockerRegistry
[Pipeline] Sets up Docker registry endpoint : End
[Pipeline] } //withEnv
[Pipeline] Set environment variables : End
[Pipeline] } //node
[Pipeline] Allocate node : End
[Pipeline] End of Pipeline
Finished: SUCCESS
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64
[JIRA] [core] (JENKINS-29647) java.lang.NoClassDefFoundError thrown by jenkins slave while the class is in the class path.
Title: Message Title David Caro commented on JENKINS-29647 Re: java.lang.NoClassDefFoundError thrown by jenkins slave while the class is in the class path. I'm having a similar issue with jenkins 1.656 and ssh agent 1.10: Caused by: java.lang.ClassNotFoundException: org.bouncycastle.openssl.PEMReader I can see though that the bouncycastle jars downloaded on the master (/var/lib/data/jenkins/plugins/ssh-agent/WEB-INF/lib/bcprov-jdk15on-1.47.jar) are version 1.47, but the jars on the slave's .jenkins/cache/jars are 1.54 (latest): Implementation-Version: 1.54.0 And yes, if I check the classes that are included in both jars, the PEMReader is only available in the old version. I have no other plugins declaring any dependency on bouncycastle, and removing the cache and reconnecting the slave redownloads the newer version to it. Any ideas? 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort commented on JENKINS-34281 Re: Queue isn't saved on any shutdown If I log the user Authentication when doing the logging upon shutdown: Principal: org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@ffc4: Username: anonymous; Password: [PROTECTED]; Authenticated: true; Details: null; Granted Authorities: anonymous Authentication name: anonymous Unfortunately by default the setup wizard disables anonymous read access: setAllowAnonymousRead(false) As of https://github.com/jenkinsci/jenkins/pull/2042/files#diff-f65b8a70854ca1cc6c12397eee54d279R62 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] [jira-trigger-plugin] (JENKINS-34301) Plugin swallows every exceptions thrown in http requests
Title: Message Title Wisen Tanasa started work on JENKINS-34301 Change By: Wisen Tanasa 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-34281 Queue isn't saved on any shutdown Change By: Sam Van Oort Assignee: Kristin Whetstone Sam Van Oort 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] [docker-workflow-plugin] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title Radesh Rao commented on JENKINS-34276 Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName() Jesse Glick: I'll try and build this patch and test out the plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort edited a comment on JENKINS-34281 Re: Queue isn't saved on any shutdown Okay, so Root cause is a permissions check failure in the getItems() method upon save shutdown. The Items don't get added to the getItems() results if they fail permissions checks (verified by logging that it does , and disabling security check there is 1 task in fixes the buildable queue , 0 waiting, 0 pending persistance) . 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] [svnmerge-plugin] (JENKINS-30769) Rebase commit message should be configurable
Title: Message Title Hugues Chabot commented on JENKINS-30769 Re: Rebase commit message should be configurable Peter Jupp some work has been done: https://github.com/jenkinsci/svnmerge-plugin/pull/29 I don't remember exactly why I did not merge the PR but if you could at least test if this PR resolve the issue for you it could really help. Thanks. 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-31601) Multibranch project or organization folder shows welcome screen immediately after configuration without refresh
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31601 Re: Multibranch project or organization folder shows welcome screen immediately after configuration without refresh This UX issues can be improved with JENKINS-34200. 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort edited a comment on JENKINS-34281 Re: Queue isn't saved on any shutdown when running with what behaves as an upgrade via mvn -f war hudson-dev:run I get a different behavior even though it plays as if it is an upgrade: the final freestyle project in the queue isn't started from on restart queue, but not lost either - it gets marked as aborted (bizarre, no?) 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort commented on JENKINS-34281 Re: Queue isn't saved on any shutdown when running with what behaves as an upgrade via mvn -f war hudson-dev:run I get a different behavior even though it plays as if it is an upgrade: the final freestyle project isn't started from queue, but not lost either - it gets marked as aborted (bizarre, no?) 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-34281) Queue isn't saved on any shutdown
Title: Message Title Sam Van Oort commented on JENKINS-34281 Re: Queue isn't saved on any shutdown Okay, so upon save, there is 1 task in the buildable queue, 0 waiting, 0 pending. 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title KK G updated an issue Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: KK G Environment: Jenkins 2.0RC1, Jenkins 1.6* LTSWindows 2008r2, Windows 2012r2, Windows 7, Windows 10 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] [svnmerge-plugin] (JENKINS-30769) Rebase commit message should be configurable
Title: Message Title peter jupp commented on JENKINS-30769 Re: Rebase commit message should be configurable Is this issue being worked on by anyone? I would be interested in making a fix to help with this scenario as it is preventing my use of the plugin with SVN repos that demand a particular commit message format e.g. commit-hook that expects a JIRA reference in the commit message. 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] [parameterized-trigger-plugin] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title squalou jenkins created an issue Jenkins / JENKINS-34340 Don't rename job names in TRIGGERED_JOB_NAMES Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/Apr/19 5:10 PM Environment: jenkins LTS 1.651.1, parameterized-trigger-plugin 2.30 master on redhat 6.4 server, slaves on redhat 7.2 Priority: Minor Reporter: squalou jenkins I'm using parameterized-trigger-plugin like this : job A runs on master , triggers job trigA on slave trigA once finised publishes some output back to master then job A goes on ...and tries to find the files published by trigA TRIGGERED_JOB_NAMES could be helpful, but why the hell replace characters from original names ? By doing so, it's impossible to use these names to build the path to trhe triggered jobs workspace.
[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title KK G updated an issue Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: KK G Environment: Jenkins 2.0RC1, Jenkins LTSWindows 2008r2, Windows 2012r2, Windows 7 , Window 10 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title KK G updated an issue Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: KK G Environment: Jenkins 2.0RC1, Jenkins LTSWindows 2008r2, Windows 2012r2, Windows 7, Window Windows 10 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title KK G updated an issue Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: KK G Environment: Jenkins 2.0RC1 , Jenkins LTS Windows 2008r2, Windows 2012r2, Windows 7 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title KK G commented on JENKINS-34150 Re: Pipeline Batch hangs Just gave a try. "workaround is to use a build agent (other than master), even being in the same physical machine." really works! Thanks. At least, I can proceed. BTW, I notice that for the same machine, master node has info, "Windows Server 2012 R2 (x86)", while client has info, "Windows Server 2012 R2 (amd64)". I doubt if the bug trigger corner case related to machine architecture. 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] [docker-workflow-plugin] (JENKINS-34289) docker.image.inside fails unexpectedly with Jenkinsfile
Title: Message Title Christian Höltje commented on JENKINS-34289 Re: docker.image.inside fails unexpectedly with Jenkinsfile Here's my "setup a test jenkins script" incase I'm doing something stupid. I use this as root and as a new user jbugs. I pull the plugins from the existing "live-ish" Jenkins to speed things up and the init.groovy.d is just setting the UpdateCenter URL to "https://updates.jenkins-ci.org/stable-1.651/update-center.json" #!/bin/bash set -euo pipefail set -x if [ "$(id -u)" = 0 ]; then jenkins_port=5000 else jenkins_port=5010 fi cd rm -rf .jenkins mkdir -p .jenkins/plugins cp -avr /var/lib/jenkins/init.groovy.d/ .jenkins/init.groovy.d/ cp -avr /var/lib/jenkins/plugins/*.jpi .jenkins/plugins/ cat < .jenkins/config.xml 1.0 1 DOCKER_HOST tcp://127.0.0.1:2375 CONFIGXML exec java -jar /var/lib/jenkins/jenkins.war --httpPort="$jenkins_port" 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-28473) Request: option to insert elements to position 0 instead of appending them
Title: Message Title Andreas Katzig commented on JENKINS-28473 Re: Request: option to insert elements to position 0 instead of appending them +1. This is definitely something we also need. Every new value which has been added should be the default value for the next build. Alternatively, Instead of "Default Choice: " add a new choice to select the value appended to the end of the list. 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-34281) Queue isn't saved on any shutdown
Title: Message Title
Sam Van Oort edited a comment on JENKINS-34281
Re: Queue isn't saved on any shutdown
So, I'm looking at how/when the save occurs. I found that the if I invoke the queue save method from the script console ( 'Jenkins.instance.queue.save()'), it correctly persists enqueued jobs:The only way this can generate the result we're seeing appears to be if no tasks are listed by this, or the queue instance being used has been cleared by another method call, or the save() method on the queue isn't invoked at the appropriate time (and a previous write overwrote it):{code:java}for (Item item: getItems()) {if(item.task instanceof TransientTask) continue;state.items.add(item);}{code}Adding log statements to save confirmed that it is the latter, adding this on Queue.java, line {code}System.out.println("Saving queue with "+state.items.size()+" items!"{code}Yielded the following on shutdown via Ctrl+C: Saving queue with 0 items! Edit: checking into it, it's not that they're Transient items, upon save, getItems().length returns 0, so does this.waitingList.size() - the queue has been cleared before saving.
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] [unity3d-plugin] (JENKINS-34339) Unable to select Unity installation
Title: Message Title first last created an issue Jenkins / JENKINS-34339 Unable to select Unity installation Issue Type: Bug Assignee: Unassigned Components: unity3d-plugin Created: 2016/Apr/19 4:53 PM Environment: OSX 10.10.5, jenkins 1.655, Unity 5.3.1f1 Priority: Blocker Reporter: first last I added the Unity3D plugin and added the build step in the project configuration. On Windows I was able to select a Unity version in the combobox labelled as Unity3d installation name. On Mac this combo box is empty and I cannot select anything. I setup jenkins for the current user instead of the user jenkins. I have several Unity versions installed and just reinstalled it. Add Comment
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for parameterized repositories
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33276 Re: Build status is not being set for parameterized repositories Code changed in jenkins User: Antonio Mansilla Path: src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/32e1ecb6616eb3d24878f1cc256c8976ac58fc02 Log: JENKINS-33276 Expands env parameters on repo URL 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-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for parameterized repositories
Title: Message Title Antonio Mansilla started work on JENKINS-33276 Change By: Antonio Mansilla 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for parameterized repositories
Title: Message Title Antonio Mansilla commented on JENKINS-33276 Re: Build status is not being set for parameterized repositories Sorry for the delay Lior Goikhburg, I finally got your problem and fixed it and it'll be included in the plugin release. Thank you for all the information you provided, it was really helpful. 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-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for parameterized repositories
Title: Message Title Antonio Mansilla resolved as Fixed Jenkins / JENKINS-33276 Build status is not being set for parameterized repositories Change By: Antonio Mansilla 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] [core] (JENKINS-34281) Queue isn't saved on any shutdown
Title: Message Title
Sam Van Oort commented on JENKINS-34281
Re: Queue isn't saved on any shutdown
So, I'm looking at how/when the save occurs. I found that the if I invoke the queue save method from the script console ( 'Jenkins.instance.queue.save()'), it correctly persists enqueued jobs:
The only way this can generate the result we're seeing appears to be if no tasks are listed by this, or the queue instance being used has been cleared by another method call, or the save() method on the queue isn't invoked at the appropriate time (and a previous write overwrote it):
for (Item item: getItems()) {
if(item.task instanceof TransientTask) continue;
state.items.add(item);
}
Adding log statements to save confirmed that it is the latter, adding this on Queue.java, line
System.out.println("Saving queue with "+state.items.size()+" items!"
Yielded the following on shutdown via Ctrl+C: Saving queue with 0 items!
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] [docker-workflow-plugin] (JENKINS-34289) docker.image.inside fails unexpectedly with Jenkinsfile
Title: Message Title
Christian Höltje edited a comment on JENKINS-34289
Re: docker.image.inside fails unexpectedly with Jenkinsfile
How about this?{code:java}node ('docker') {def img = docker.image('busybox');img.pull();img.inside {sh 'for i in $(seq 30); do sleep 1; echo $i; done';}}{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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for parameterized repositories
Title: Message Title Antonio Mansilla updated an issue Jenkins / JENKINS-33276 Build status is not being set for parameterized repositories Change By: Antonio Mansilla Issue Type: Bug Improvement 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] [docker-workflow-plugin] (JENKINS-34289) docker.image.inside fails unexpectedly with Jenkinsfile
Title: Message Title Christian Höltje commented on JENKINS-34289 Re: docker.image.inside fails unexpectedly with Jenkinsfile Interesting. At the moment I don't have slaves; I'm using master to build stuff... Jenkins is running as the non-root user jenkins and using DOCKER_HOST=tcp://127.0.0.1:2375 via configuring the master node. If I stand up a clean Jenkins running as root then my example code works. If I stand up a clean Jenkins running as a non-root user, then my example code fails on the first sleep 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] [android-lint-plugin] (JENKINS-33311) Jenkins Pipeline (Workflow) support for Android Lint Plugin plugin
Title: Message Title jared welch commented on JENKINS-33311 Re: Jenkins Pipeline (Workflow) support for Android Lint Plugin plugin Thank you! That will be very helpful as we use it currently in our freestyle projects, but we are switching to 100% pipeline projects very soon. 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-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for parameterized repositories
Title: Message Title Antonio Mansilla updated an issue Jenkins / JENKINS-33276 Build status is not being set for parameterized repositories Change By: Antonio Mansilla Summary: Build status is not being set for commit in bitbucket parameterized repositories 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] [android-lint-plugin] (JENKINS-33311) Jenkins Pipeline (Workflow) support for Android Lint Plugin plugin
Title: Message Title Christopher Orr commented on JENKINS-33311 Re: Jenkins Pipeline (Workflow) support for Android Lint Plugin plugin jared welch: Yes, I planned on doing it this week. But I think there's a bug in the Pipeline functionality that got added, which means that the overall results are displayed, but the details can't be viewed. So I'd like to test that further and hopefully find a fix for it. 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-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Patrick Wolf commented on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
gitt You can update the whitelist with a plugin:
@Extension
public static class MiscWhitelist extends ProxyWhitelist {
/**
* Methods to add to the script-security whitelist for this plugin to work.
*
* @throws IOException
*/
public MiscWhitelist() throws IOException {
super(new StaticWhitelist(
"method java.util.Map containsKey java.lang.Object",
"method java.lang.Class isInstance java.lang.Object"
}
}
If you encapsulate your whitelist in a plugin then you simply need to install the plugin on each master where you want to apply it.
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] [extended-choice-parameter-plugin] (JENKINS-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z updated an issue Jenkins / JENKINS-34199 Cannot use a simple Groovy Script Change By: Dav z Comment: [~vimil] I noticed that you are using a windows based system.As I am on opensuse 12.2 , can it be that is a system dependent issue? I tried with a simple script in my workspace folder, used the full path but nothing comes up. No errors, nothing comes up. Everything works ok if I put the script inlne. Is there anything that I can look for, any special debug ? 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] [android-lint-plugin] (JENKINS-33311) Jenkins Pipeline (Workflow) support for Android Lint Plugin plugin
Title: Message Title jared welch commented on JENKINS-33311 Re: Jenkins Pipeline (Workflow) support for Android Lint Plugin plugin Christopher Orr Do you have an ETA for the 2.3 release? 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] [docker-workflow-plugin] (JENKINS-34288) docker pull gives "Scripts not permitted to use new" error
Title: Message Title Christian Höltje resolved as Cannot Reproduce Jenkins / JENKINS-34288 docker pull gives "Scripts not permitted to use new" error Change By: Christian Höltje Status: Open 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] [docker-workflow-plugin] (JENKINS-34288) docker pull gives "Scripts not permitted to use new" error
Title: Message Title Christian Höltje commented on JENKINS-34288 Re: docker pull gives "Scripts not permitted to use new" error I cannot reproduce on a clean version of Jenkins. Maybe I had an older version of the plugin for some reason? 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] [docker-workflow-plugin] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Jesse Glick commented on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Proposed patch:
diff --git a/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy b/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy
index 5842ed5..6a84158 100644
--- a/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy
+++ b/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy
@@ -109,7 +109,7 @@ class Docker implements Serializable {
// withDockerContainer requires the image to be available locally, since its start phase is not a durable task.
pull()
}
-docker.script.withDockerContainer(image: id, args: args, toolName: docker.script.env.DOCKER_TOOL_NAME) {
+docker.script.withDockerContainer(image: imageName(), args: args, toolName: docker.script.env.DOCKER_TOOL_NAME) {
body()
}
}
but need to figure out how to reproduce the problem to verify the fix.
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] [ec2-plugin] (JENKINS-25832) Launch multiple slaves in parallel for jobs with same node label
Title: Message Title Joshua Ma commented on JENKINS-25832 Re: Launch multiple slaves in parallel for jobs with same node label Agreed! Right now I'm running a few permanent slaves to help with this, but it'd be great if the EC2 plugin's response scaled with the # of pending builds. Otherwise, it seems like it'll wait a few minutes to determine a new machine is needed, wait a few minutes to determine a new machine is needed, and so on. 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] [docker-workflow-plugin] (JENKINS-34289) docker.image.inside fails unexpectedly with Jenkinsfile
Title: Message Title Christian Höltje commented on JENKINS-34289 Re: docker.image.inside fails unexpectedly with Jenkinsfile I'm pretty sure that the shell step isn't even executed inside the container and that AbortException is being returned from something else. If I change the step to run sleep 1 || true it still aborts with -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.
