[JIRA] [xcode-plugin] (JENKINS-26368) Technical Version / Marketing Version Not Updating
lacostej commented on JENKINS-26368 Technical Version / Marketing Version Not Updating James, should I close this as a cocoapods issue. Have you tried to check the file format of the xcproject before and after you run your cocoapods command ? We could update the plugin to display a warning of the avgtool fails to do its intended operation. It looks like it does nothing special: https://github.com/jenkinsci/xcode-plugin/blob/master/src/main/java/au/com/rayh/XCodeBuilder.java#L343 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
ngiger commented on JENKINS-23577 Add support for using branches in Git Parameter plugin Please use the newly released version 0.4.0 and comment whether your are satisfied with the solution or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger commented on JENKINS-23396 SSH credentials not supported I finally found some time to dig into some pending issues of the git-parameter plugins. I could reproduce the problem here. Will investigate the 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly
ngiger commented on JENKINS-24544 GIT revisions list empty while GIT tags list populated correctly Can you try whether upgrading to 0.4.0 solves your problem or not? Otherwise would it be possible give the URL where your experience this problem. I suspect that we have a weird git commit with a comment that causes havoc. Or you could checkout the git-parameter plugin, add lines like LOGGER.log(Level.INFO, "generateContents add SHA1 " + r.getSha1String()); LOGGER.log(Level.INFO, "generateContents add prettyRevisionInfo " + r.prettyRevisionInfo(newgit, r)); before the calls to paramList.put. Then call mvn clean install to build the plugin. And test it by adding the target/git-parameter.hpi via http://jenkins-url/pluginManager/advanced. The output of the jenkins log should then more details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-14624) TFS plugin needs overwrite option for writable files on workspace
Karl-Heinz Marbaise commented on JENKINS-14624 TFS plugin needs overwrite option for writable files on workspace I have observed the same thing. I don't know why files are marked rw but the problem exists and it's really time consuming to smash away the workspace and let recreate it..Currently in our build it takes ca. 6 minutes to create a new workspace with all files whereas our build take 10 minutes. So this would be a greate feature. On the other hand the question is: How can files being marked rw if they are not being changed in the workspace in Jenkins. How could files become rw ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
SCM/JIRA link daemon commented on JENKINS-23396 SSH credentials not supported Code changed in jenkins User: Niklaus Giger Path: pom.xml src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/67d0443473a4f989f3e6da18f362b62c6194f16c Log: JENKINS-23396Get credentials before fetching info This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger commented on JENKINS-23396 SSH credentials not supported Should be fixed with commit https://github.com/jenkinsci/git-parameter-plugin/commit/67d0443473a4f989f3e6da18f362b62c6194f16c. If you have time and know how to test drive it, I would appreciate a feedback. I will wait about a week till I will publish a new version, in case any problem pops up in the mean time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger started work on JENKINS-23396 SSH credentials not supported Change By: ngiger (17/Jan/15 11:02 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
ngiger started work on JENKINS-23577 Add support for using branches in Git Parameter plugin Change By: ngiger (17/Jan/15 11:02 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24502) Specify a local subdir to check the git repo
ngiger closed JENKINS-24502 as Not A Defect Specify a local subdir to check the git repo Change By: ngiger (17/Jan/15 11:07 AM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24502) Specify a local subdir to check the git repo
ngiger commented on JENKINS-24502 Specify a local subdir to check the git repo For this kind of task you should use the "Additional Behaviours" (Select Checkout to sub-directory) of the git plugin. Therefore I will close this 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-20958) Allow to choose from branches and not only shas and tags
ngiger commented on JENKINS-20958 Allow to choose from branches and not only shas and tags This should be solved with the just release version 0.4.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-20958) Allow to choose from branches and not only shas and tags
ngiger closed JENKINS-20958 as Fixed Allow to choose from branches and not only shas and tags This should be solved with the just release version 0.4.0 Change By: ngiger (17/Jan/15 11:08 AM) Status: Open Closed 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
ngiger commented on JENKINS-23188 Tag List Empty I pushed commit to add the credentials before fetching the tag items. https://github.com/jenkinsci/git-parameter-plugin/commit/67d0443473a4f989f3e6da18f362b62c6194f16c will probably release 0.4.1 in a week or so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
ngiger closed JENKINS-23188 as Duplicate Tag List Empty Seemd to be a duplicate of 23188 Change By: ngiger (17/Jan/15 11:17 AM) Status: Open Closed 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
ngiger commented on JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves Can you give version 0.4.0 a try whether the problem still persists? If yes, I will try to fix in the next few weeks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26448) Cannot use git in Jenkins
Guy Van Sanden commented on JENKINS-26448 Cannot use git in Jenkins @Mark I upgraded to the latest weekly and upgraded all plugins, it makes no difference @Daniel Restarting and rebooting has no effect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26448) Cannot use git in Jenkins
Mark Waite commented on JENKINS-26448 Cannot use git in Jenkins Any chance you've disabled one or more of your plugins? There was a report a while ago that installing and then disabling one of the credential related plugins would cause a class loading exception when the git client plugin was loaded. The description was that the git client depended on another plugin and if that plugin was disabled, then the git client Java classes could not be initialized because their dependencies could not be satisfied. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26448) Cannot use git in Jenkins
Mark Waite edited a comment on JENKINS-26448 Cannot use git in Jenkins Any chance you've disabled one or more of your plugins? There was a report a while ago that installing and then disabling one of the credential related plugins would cause a class loading exception when the git client plugin was loaded. The description was that the git client depended on another plugin and if that plugin was disabled, then the git client Java classes could not be initialized because their dependencies could not be satisfied. You might refer to JENKINS-21745 and JENKINS-22017 for discussion which might be related. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
amit gilad edited a comment on JENKINS-26304 Output variables missing while using AWS CloudFormation as build-step Hi Or Tzabary i am working on fixing this issue but can you please attach an example of what you are trying to do so i can check it out This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
amit gilad commented on JENKINS-26304 Output variables missing while using AWS CloudFormation as build-step Hi Or Tzabary i am working on fixing this issue but can you please send me an example of what you are trying to do so i can check it out This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26448) Cannot use git in Jenkins
Guy Van Sanden commented on JENKINS-26448 Cannot use git in Jenkins Thank you Mark! The error is gone after installing the ssh-credentials 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/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
amit gilad edited a comment on JENKINS-26304 Output variables missing while using AWS CloudFormation as build-step Hi Or I tried it with a few scenarios and it worked for me, can you please attach an example of what you are trying to do so i can check it out This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26448) Cannot use git in Jenkins
Mark Waite resolved JENKINS-26448 as Not A Defect Cannot use git in Jenkins Change By: Mark Waite (17/Jan/15 5:21 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26448) Cannot use git in Jenkins
Mark Waite closed JENKINS-26448 as Not A Defect Cannot use git in Jenkins Change By: Mark Waite (17/Jan/15 5:21 PM) Status: Resolved 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) First time build does not show changelog
Mark Waite resolved JENKINS-26354 as Wont Fix First time build does not show changelog There isn't any way to reliably decide which branch should be the basis for the diff calculation you're proposing for an initial branch. There may be many different heuristics (fallible rules) which could be applied to the case, but there will be cases where each of the heuristics is wrong. Change By: Mark Waite (17/Jan/15 5:23 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-25722) CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact
Michael Clarke closed JENKINS-25722 as Cannot Reproduce CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact Since no-one else has reported this, and I've not been able to reproduce this, I'm closing this issue. If anyone has any further details that will help replicate this issue then feel free to provide them and re-open this issue. Change By: Michael Clarke (17/Jan/15 7:15 PM) Status: Open Closed Assignee: MichaelClarke Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-17383) CVS plugin detect changes in 'rlog' but not in 'update'
Michael Clarke resolved JENKINS-17383 as Fixed CVS plugin detect changes in rlog but not in update Re-closing issue. Latest comment was unrelated, duplicated in another issue, and does not provide enough information to allow the issue to be replicated. Change By: Michael Clarke (17/Jan/15 7:20 PM) Status: Reopened 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-15349) missing maven 2/3 job type from the list of available type for a new job
SHIRAZ HAIDER commented on JENKINS-15349 missing maven 2/3 job type from the list of available type for a new job Any update on how to resolve this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-26347) Credentials not found for merge from mainline
Hugues Chabot commented on JENKINS-26347 Credentials not found for merge from mainline Can you confirm that the build was run on a slave ? If yes, can you tell me what kind of slave and if you have the same problem when the build runs on the master. Also, can you tell me the protocol of the SVN URL ? http, https, svn ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1
Eric Theriault commented on JENKINS-22328 ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1 For other searchers, the recipe in JENKINS-19329 resolved this issue for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Tommy McNeely commented on JENKINS-23396 SSH credentials not supported Hi @ngiger: If you have any "documentation" on how to test this, we could test. We are currently on LTS Jenkins via RPM on CentOS. If there is an "installable" version of this module somewhere, we could give it a try. If it involves setting up a development environment, I am out, I tried to do some of that to look into the "Folders" bug, and figured out I have no business in there ~tommy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
