[JIRA] [build-token-root] (JENKINS-18008) Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1'
Stuart Montgomery updated JENKINS-18008 Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1' Change By: Stuart Montgomery (19/May/13 8:36 AM) Summary: Builds triggered using token with this build-token-root plugin show remote host as '127.0.0.1' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-token-root] (JENKINS-18008) Builds triggered using token with this plugin show remote host as '127.0.0.1'
Stuart Montgomery created JENKINS-18008 Builds triggered using token with this plugin show remote host as '127.0.0.1' Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Attachments: c934e4d2-bec0-11e2-84fc-952ab3cb691a.png Components: build-token-root Created: 19/May/13 8:36 AM Description: Builds triggered using per-project token via the API provided by this plugin show their remote host as '127.0.0.1' rather than the real IP the build was started from. In my case, I ran curl(1) to trigger the build from another machine, and it still shows up as 127.0.0.1 (localhost), see attached screenshot. I am accessing this Jenkins instance via an Apache reverse proxy so that I can use SSL. But I believe my Apache virtual host is configured properly to set proxy headers like X-Forwarded-For, etc. (per http://httpd.apache.org/docs/trunk/mod/mod_proxy.html). My Apache config includes the following: ProxyRequests On ProxyPreserveHost On ProxyPass / http://localhost:8080/ retry=0 ProxyPassReverse / http://localhost:8080/ Is Jenkins not respecting the X-Forwarded-* HTTP headers when determining the remote IP? That may be the root cause here. Environment: Jenkins 1.514, Oracle Linux, accessed via reverse Apache proxy (for SSL) Project: Jenkins Priority: Minor Reporter: Stuart Montgomery This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Joris De Winne commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Martin, I've implemented a fix for this. So this will be fixed with the next release of the plugin. If you want you can checkout the code and use the latest version from github. Regards, Joris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-4409) Hudson test case leaks temp folders
ikedam commented on JENKINS-4409 Hudson test case leaks temp folders I think that TestPluginManager doesn't need to use different directories every time. Using a fixed directory resolves the increase of temporary files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
Rino commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter The pull request is still open. In the meantime you could build the snapshot from source: https://github.com/rinokadijk/rebuild-plugin.git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rebuild] (JENKINS-14419) Error code 403 when trying to rebuild a job from the pipeline view
Rino commented on JENKINS-14419 Error code 403 when trying to rebuild a job from the pipeline view Could you try upgrading to rebuild plugin 1.19 and see if the error still occurs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rebuild] (JENKINS-7703) Parameters passed through the Parameterized trigger plugin are not reused by rebuild plugin
Rino resolved JENKINS-7703 as Fixed Parameters passed through the Parameterized trigger plugin are not reused by rebuild plugin Change By: Rino (19/May/13 10:17 AM) Status: Open Resolved Assignee: ragesh_nair Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-token-root] (JENKINS-18008) Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1'
Mirko Friedenhagen commented on JENKINS-18008 Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1' See https://github.com/jenkinsci/jenkins/pull/239 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-4409) Hudson test case leaks temp folders
ikedam commented on JENKINS-4409 Hudson test case leaks temp folders Sent a pull request to make TestPluginManager use a fixed directory. https://github.com/jenkinsci/jenkins/pull/780 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-token-root] (JENKINS-18008) Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1'
Mirko Friedenhagen updated JENKINS-18008 Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1' Change By: Mirko Friedenhagen (19/May/13 12:49 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-token-root] (JENKINS-18008) Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1'
Mirko Friedenhagen edited a comment on JENKINS-18008 Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1' I do not think this is a plugin problem, but should probably be fixed in core: https://github.com/jenkinsci/jenkins/pull/239. I think Koshuke was not sure whether this would be a security issue. One could argue, that this is quite safe, when remote address is 127.0.0.1. However I do not see real security issues here, as this is only for the Build Cause. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [managed-scripts] (JENKINS-18004) Managed Scripts does not use Token macros
SCM/JIRA link daemon commented on JENKINS-18004 Managed Scripts does not use Token macros Code changed in jenkins User: imod Path: pom.xml src/main/java/org/jenkinsci/plugins/managedscripts/ScriptBuildStep.java http://jenkins-ci.org/commit/managed-scripts-plugin/c6150ef1d11125e9a9530b75e7bc5224b6add353 Log: [FIXED JENKINS-18004] add support for TokenMacros This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [managed-scripts] (JENKINS-18004) Managed Scripts does not use Token macros
SCM/JIRA link daemon resolved JENKINS-18004 as Fixed Managed Scripts does not use Token macros Change By: SCM/JIRA link daemon (19/May/13 2:30 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [managed-scripts] (JENKINS-17561) Arguments are lost within conditional step
domi resolved JENKINS-17561 as Duplicate Arguments are lost within conditional step this is a duplicate of JENKINS-15995 which was fixed with version 1.0.2 Change By: domi (19/May/13 2:36 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18008) Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1'
Stuart Montgomery updated JENKINS-18008 Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1' Change By: Stuart Montgomery (19/May/13 4:23 PM) Assignee: Jesse Glick Component/s: build-token-root This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18008) Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1'
Stuart Montgomery commented on JENKINS-18008 Builds triggered using token with build-token-root plugin show remote host as '127.0.0.1' Agreed, can we integrate Mirko's pull request? That will likely solve the issue, and I can't imagine how it will be a security issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-17708) Expose scriptler scripts via token macro token
SCM/JIRA link daemon commented on JENKINS-17708 Expose scriptler scripts via token macro token Code changed in jenkins User: imod Path: .gitignore pom.xml src/main/java/org/jenkinsci/plugins/scriptler/ScriptlerManagment.java src/main/java/org/jenkinsci/plugins/scriptler/tokenmacro/ScriptlerTokenMacro.java src/main/java/org/jenkinsci/plugins/scriptler/util/GroovyScript.java src/main/resources/org/jenkinsci/plugins/scriptler/Messages.properties src/test/java/org/jenkinsci/plugins/scriptler/ScriptlerManagementHelper.java src/test/java/org/jenkinsci/plugins/scriptler/tokenmacro/ScriptlerTokenMacroTest.java http://jenkins-ci.org/commit/scriptler-plugin/1f5a83c5ab43c04a00113f087bb0d22db0b87193 Log: [FIXED JENKINS-17708] Expose scriptler scripts via token macro token This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-17708) Expose scriptler scripts via token macro token
SCM/JIRA link daemon resolved JENKINS-17708 as Fixed Expose scriptler scripts via token macro token Change By: SCM/JIRA link daemon (19/May/13 5:43 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17988) Broken image links when using CloudBees Folders plugin
SCM/JIRA link daemon commented on JENKINS-17988 Broken image links when using CloudBees Folders plugin Code changed in jenkins User: Marco Ambu Path: src/main/resources/hudson/plugins/view/dashboard/jobLink.jelly http://jenkins-ci.org/commit/dashboard-view-plugin/8b830d2870d310eb829916bceceba6bb172000b6 Log: Merge pull request #15 from jglick/folders-JENKINS-17988 [FIXED JENKINS-17988] Use appropriate icon construction methods Compare: https://github.com/jenkinsci/dashboard-view-plugin/compare/8ac89f359a89...8b830d2870d3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17314) Rebuild Job using GET method
Marco Ambu commented on JENKINS-17314 Rebuild Job using GET method 2.6 is out there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger 0.28 seems to do the trick. Happy days This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14201) Git submodules checked out in wrong place
Mark Waite commented on JENKINS-14201 Git submodules checked out in wrong place I attempted to create a Jenkins 1.509.1 job with git-client-plugin 1.0.6 and git-plugin 1.4.0 using git://github.com/alexbirkett/phonelocator-android.git and enabling processing of submodules in the Jenkins job definition. It fails to checkout the source code because one or more of the referenced repositories seem to no longer exist. Since Arkadiy says it works for him and there has been no counter-response from Alex, I recommend this bug be closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14201) Git submodules checked out in wrong place
Mark Waite resolved JENKINS-14201 as Fixed Git submodules checked out in wrong place Reported resolved by Arkady in March 2013. Change By: Mark Waite (19/May/13 9:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-2673) Invalid CRON Warnings
daniel carter commented on JENKINS-2673 Invalid CRON Warnings This wording is very confusing. For the common case of * * * * *, i thought it was suggesting 0 * * * * is the correct configuration to enable polling every minute, until my brain told me no that would be hourly. How many people with no prior unix cron experience have set followed the suggestion, and then wondered why it's not running every minute? If it is trying to suggest that per minute polling is bad practise, the message should at least mention the suggestion is for every hour. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-3481) Incorrect WebSVN path generation
daniel carter commented on JENKINS-3481 Incorrect WebSVN path generation Can we get the WebSVN browser that is included removed from the SVN plugin. It's annoying to see that WebSVn support is there and spend ages trying to fix the problem where it's appending a / to the URL and then after a few searches finding that it's a known issue and you have to install WebSVN2 to get a working version. It would be much easier if there was no WebSVN support in the base system and then users would check available plugins and find the working WebSVN2 plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Vlad Aginsky assigned JENKINS-17526 to IRCbot Run by Kohsuke Broken CSS when reloading Jenkins after a time of inactivity Change By: Vlad Aginsky (20/May/13 5:22 AM) Assignee: IRCbot Run by Kohsuke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Vlad Aginsky updated JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session this is how it looks for me at chrome Version 26.0.1410.64 m Change By: Vlad Aginsky (20/May/13 6:40 AM) Attachment: jenkins-gui.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-2556) Use svn switch where applicable
Matt Doran commented on JENKINS-2556 Use svn switch where applicable Any thoughts pushing a new build of the SVN plugin that includes this fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Vlad Aginsky edited a comment on JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session this is how it looks for me at chrome Version 26.0.1410.64 m(attached) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Vlad Aginsky edited a comment on JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session this is how it looks for me at chrome Version 26.0.1410.64 m(attached jenkins-gui.png) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
