[JIRA] (JENKINS-36118) console output for a job run reports error

2016-06-25 Thread stevengbr...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven G Brown commented on  JENKINS-36118  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: console output for a job run reports error   
 

  
 
 
 
 

 
 It looks like the TimestampAnnotatorFactory class is still loaded from an earlier version of Timestamper. I haven't been able to reproduce this so far. How did you perform the upgrade?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-35509) ci skip is not working

2016-06-25 Thread rameshbabu.tho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramesh Babu stopped work on  JENKINS-35509  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ramesh Babu  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-35509) ci skip is not working

2016-06-25 Thread rameshbabu.tho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramesh Babu started work on  JENKINS-35509  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ramesh Babu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34166) Allow restart aborted builds for cancelled builds

2016-06-25 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam commented on  JENKINS-34166  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow restart aborted builds for cancelled builds   
 

  
 
 
 
 

 
 Released as build-timeout 1.17. You need install naginator-plugin to enable the feature. Please try that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-8947) Allow a build to be restarted X amount of times if it times out

2016-06-25 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-8947  
 
 
  Allow a build to be restarted X amount of times if it times out   
 

  
 
 
 
 

 
Change By: 
 ikedam  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-8947) Allow a build to be restarted X amount of times if it times out

2016-06-25 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released as build-timeout 1.17.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-8947  
 
 
  Allow a build to be restarted X amount of times if it times out   
 

  
 
 
 
 

 
Change By: 
 ikedam  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace

2016-06-25 Thread jacob.kel...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Keller commented on  JENKINS-27668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support for multiple git repositories in a single workspace   
 

  
 
 
 
 

 
 I'm not saying it's the best or that it couldn't be improved, but it's what we have today that doesn't require more work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33230) Jenkins creates lots of warning message for creating matrix project root directory

2016-06-25 Thread anthonylee.wall...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Wallace commented on  JENKINS-33230  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins creates lots of warning message for creating matrix project root directory   
 

  
 
 
 
 

 
 Update 1.7.1 of Matrix Project plugin looks like it contains the fix. I have not tried it yet but will report back, hopefully by tomorrow.  Jenkins 1.651.3/Matrix Project 1.7/Java 7/Linux VM  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36224) Environment variables not visible / linked for pipeline jobs

2016-06-25 Thread marc.es...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marc Esher created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36224  
 
 
  Environment variables not visible / linked for pipeline jobs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Manuel Recena Soto  
 
 
Components: 
 workflow-multibranch-plugin, workflow-plugin  
 
 
Created: 
 2016/Jun/25 6:52 PM  
 
 
Environment: 
 Jenkins 2.10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marc Esher  
 

  
 
 
 
 

 
 In other job types, for a given build, if the EnvInject plugin is installed then "Environment variables" shows up as a link on the left sidebar. In addition, if Build Environment plugin is installed, it'll add a "Compare Environment" link to builds that lets you easily compare environment variables across builds. Both of these are very useful for troubleshooting build problems, but they're missing from Pipeline jobs. Not sure if this is something about Pipeline plugins themselves, or if those two plugins need to be updated to support pipeline jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 


[JIRA] (JENKINS-35345) Allow to automatically purge old bundles

2016-06-25 Thread minudika...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Minudika Malshan started work on  JENKINS-35345  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Minudika Malshan  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33394) Generate support bundle before providing download

2016-06-25 Thread minudika...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Minudika Malshan assigned an issue to Minudika Malshan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33394  
 
 
  Generate support bundle before providing download   
 

  
 
 
 
 

 
Change By: 
 Minudika Malshan  
 
 
Assignee: 
 Steven Christou Minudika Malshan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36223) Can no longer run maven build after update to 2.8

2016-06-25 Thread thomas.biesa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Biesaart closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Not a bug in jenkins but in a plugin  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36223  
 
 
  Can no longer run maven build after update to 2.8   
 

  
 
 
 
 

 
Change By: 
 Thomas Biesaart  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit 

[JIRA] (JENKINS-36223) Can no longer run maven build after update to 2.8

2016-06-25 Thread thomas.biesa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Biesaart commented on  JENKINS-36223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can no longer run maven build after update to 2.8   
 

  
 
 
 
 

 
 Turns out this is caused by the artifactory maven plugin. There is an issue here: https://www.jfrog.com/jira/browse/HAP-771  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36223) Can no longer run maven build after update to 2.8

2016-06-25 Thread thomas.biesa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Biesaart updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36223  
 
 
  Can no longer run maven build after update to 2.8   
 

  
 
 
 
 

 
Change By: 
 Thomas Biesaart  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36223) Can no longer run maven build after update to 2.8

2016-06-25 Thread thomas.biesa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Biesaart created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36223  
 
 
  Can no longer run maven build after update to 2.8   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 consoleText.txt  
 
 
Components: 
 maven-plugin  
 
 
Created: 
 2016/Jun/25 1:40 PM  
 
 
Environment: 
 Version: 2.8  OS: Both Windows and Ubuntu  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Thomas Biesaart  
 

  
 
 
 
 

 
 I just updated to 2.10 and the next maven build failed. This exact error happened with two different configurations on two different systems. I downgraded to 2.8 to see if it was the same there and the answer is yes. Whenever I start a maven build I get a big stack trace and the build fails. An example: http://jenkins.chapp.io/job/PCS4J/14/console I included the log text for completeness sake  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue

2016-06-25 Thread nbharath....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bharath Natarajan commented on  JENKINS-36215  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Weblogic Deployer plugin 3.3 issue   
 

  
 
 
 
 

 
 Hi Raphel Chaumier, Yes, the job which deploys is running only on slave node at present. Yes, it would be fine even if we can run it from Master, but it would better if we can run it only on slave node, as we wanted Master to be isolated as it connects to multiple other slaves. Also, I observed that in a similar jenkins configuration where both Master and Slave servers are hosted on Windows, JAVA_HOME is being taken from Slave node which is not happening in our case where Master is on Linux and Slave is on Windows. Even though we tried referring to Slave node JAVA_HOME in Jenkins Global Configuration, it was not taking it up. I am not sure if this difference is due to the fact that Master and Slaves runs on different Operating System.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue

2016-06-25 Thread r...@orange.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael CHAUMIER edited a comment on  JENKINS-36215  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Weblogic Deployer plugin 3.3 issue   
 

  
 
 
 
 

 
 HI [~bharath_natarajan]As you can see in the log, the problem is that your slave (on windows) doesn't found the binary java which is set with a *nix path.  ( a jdk tool in global jenkins configuration or the JAVA_HOME)  java.io.IOException: Cannot run program "/usr/java/jdk1.8.0_25/jre/bin/java": CreateProcess error=2, The system cannot find the file specifiedIs the job which deploys only run on slave ? If you run this on master is it ok?  Regards  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue

2016-06-25 Thread r...@orange.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael CHAUMIER commented on  JENKINS-36215  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Weblogic Deployer plugin 3.3 issue   
 

  
 
 
 
 

 
 HI Bharath Natarajan As you can see in the log, the problem is that your slave (on windows) doesn't found the binary java which is set with a *nix path.  java.io.IOException: Cannot run program "/usr/java/jdk1.8.0_25/jre/bin/java": CreateProcess error=2, The system cannot find the file specified Is the job which deploys only run on slave ? If you run this on master is it ok? Regards  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36222) Login failed for Jenkins

2016-06-25 Thread manju4selen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manju G resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36222  
 
 
  Login failed for Jenkins   
 

  
 
 
 
 

 
Change By: 
 Manju G  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36222) Login failed for Jenkins

2016-06-25 Thread manju4selen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manju G started work on  JENKINS-36222  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Manju G  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36222) Login failed for Jenkins

2016-06-25 Thread manju4selen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manju G created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36222  
 
 
  Login failed for Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Manju G  
 
 
Components: 
 jenkins-cloudformation  
 
 
Created: 
 2016/Jun/25 7:32 AM  
 
 
Environment: 
 Jenkins  
 
 
Labels: 
 security  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Manju G  
 

  
 
 
 
 

 
 Login Failed 1.Invalid user and Password. 2.Forgot user and password.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-36222) Login failed for Jenkins

2016-06-25 Thread manju4selen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manju G updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36222  
 
 
  Login failed for Jenkins   
 

  
 
 
 
 

 
Change By: 
 Manju G  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.