[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Ian Norton commented on JENKINS-7641 Slaves hang when archiving artifacts Hmm.. my windows slaves are the ones mostly (but not exclusivly) involved in this bug. All my windows slaves are using Oracle Java 1.7. My master is oepnjdk 1.7 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Ian Norton edited a comment on JENKINS-7641 Slaves hang when archiving artifacts Hmm.. my windows slaves are the ones mostly (but not exclusivly) involved in this bug. All my windows slaves are using Oracle Java 1.7. My master is oepnjdk 1.7 on 64bit linux 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Oliver Bock commented on JENKINS-7641 Slaves hang when archiving artifacts Unfortunately Oracle Java isn't available on OS X 10.7 but we only see the issue on 10.4 - and we still need to support it. 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Oliver Bock edited a comment on JENKINS-7641 Slaves hang when archiving artifacts Unfortunately Oracle Java isn't available on OS X 10.7 but we only see the issue (1, 2) on 10.4 - and we still need to support it. 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Oliver Bock edited a comment on JENKINS-7641 Slaves hang when archiving artifacts Unfortunately Oracle Java isn't available on OS X 10.7 but we only see the issue (see above: comment 1, comment 2) on 10.4 - and we still need to support it. 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Joe Croft commented on JENKINS-7641 Slaves hang when archiving artifacts And the beat goes on... I am getting the same exception with Ubunto 12.04 remote and a Jenkins 1.509.1 master... sigh, I know it's an older master but still, yet another data point. This project worked and archived 25 days ago without any problem. Now it won't pass for nothing. 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Daniel Beck commented on JENKINS-7641 Slaves hang when archiving artifacts Is anyone experiencing this on Oracle JDK? Quoting an earlier comment: We had a similar issue to this that was resolved by switching to Oracle's JDK from Open JDK. That would be a real data point... 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Ian Norton commented on JENKINS-7641 Slaves hang when archiving artifacts I'm getting this about once every three or four builds now, mostly with windows (cygwin) slaves but not exclusively. My artifacts range from 1-2 mb to 800mb. Size appears not to be an issue. At the time things hang (forever) both master and slave become quiet. Other jobs on other slaves progress without issue. When I cancel the stuck build I see: ERROR: Failed to archive artifacts: pool.tar.gz,*/.log,built.,pool//-Results.xml,_pool.tar.gz,.html,*.st java.io.IOException: java.io.IOException: Failed to extract . snip Caused by: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:177) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) snip Will pfalcon's patch cure 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Gene Ratzlaff commented on JENKINS-7641 Slaves hang when archiving artifacts Like mjmac, hangs after "Archiving artifacts" if I don't have "Response Time" checked under "Preventive Node Monitoring" for my slave nodes. However, if the monitoring is enabled, I get the IOException. Happens more often than not, but is intermittent. If I use my Jenkins master (jenkins-1.549-1.1; Intel server with RHEL 6.4) as a slave I don't see any issues, ever. My other slaves are IBM PPC servers (also with RHEL6.4) - that's where I see the problem. I've only tested with a 20-byte file, so size isn't the issue. If I kill a hung job I get the following: Archiving artifacts ERROR: Failed to archive artifacts: the_date.txt java.io.IOException: java.io.IOException: Failed to extract /bgusr/home1/jenkins/bgqmsn0/workspace/gene_triggerer2/transfer of 1 files at hudson.FilePath.readFromTar(FilePath.java:2088) at hudson.FilePath.copyRecursiveTo(FilePath.java:2000) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:175) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) at hudson.FilePath.readFromTar(FilePath.java:2066) ... 12 more at hudson.FilePath.copyRecursiveTo(FilePath.java:2007) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request$1.get(Request.java:278) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:2003) ... 11 more Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at
[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Paul Sokolovsky commented on JENKINS-7641 Slaves hang when archiving artifacts Woo-hoo, the patch in the previous comment works: 00:18:59.873 FATAL: HTML Publisher failure 00:18:59.873 hudson.util.IOException2: hudson.util.IOException2: Failed to extract /srv/jenkins/workspace/job/doc/html/*/ 00:18:59.873 at hudson.FilePath.readFromTar(FilePath.java:2066) 00:18:59.873 at hudson.FilePath.copyRecursiveTo(FilePath.java:1978) 00:18:59.873 at hudson.FilePath.copyRecursiveTo(FilePath.java:1889) 00:18:59.873 at hudson.FilePath.copyRecursiveTo(FilePath.java:1872) 00:18:59.873 at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:213) 00:18:59.873 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:18:59.873 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 00:18:59.873 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) 00:18:59.873 at hudson.model.Build$BuildExecution.post2(Build.java:183) 00:18:59.873 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 00:18:59.873 at hudson.model.Run.execute(Run.java:1690) 00:18:59.873 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 00:18:59.873 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:18:59.873 at hudson.model.Executor.run(Executor.java:246) 00:18:59.873 Caused by: java.io.IOException: High-level timeout waiting for activity on pipe 00:18:59.873 at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:180) 00:18:59.873 at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) 00:18:59.873 at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:175) 00:18:59.873 at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) 00:18:59.873 at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) 00:18:59.873 at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) 00:18:59.873 at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) 00:18:59.873 at hudson.FilePath.readFromTar(FilePath.java:2044) 00:18:59.873 ... 13 more So, the timeout as it is now is 1000s. Trying to cut that in 2 and see if any false positive timeouts would happen. 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Paul Sokolovsky commented on JENKINS-7641 Slaves hang when archiving artifacts Ok, so this is probably as old as Jenkins itself, and probably ready to become (if not already) its businesscard - what's that Jenkins thing? Ah, it does some CI and bunch of server hanging around. And the biggest problem is not that the issue described here happens, it's what shown by this log: 01:53:56.709 Archiving artifacts 12:02:21.094 ERROR: Failed to archive artifacts: *.sum 12:02:21.096 hudson.util.IOException2: hudson.util.IOException2: Failed to extract /home/buildslave/workspace/cbuild/transfer of 1 files 12:02:21.096 Caused by: java.io.IOException 12:02:21.096 at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) So, it hanged build server for 10hrs. As it usually happens, there're more jobs accumulate for this build slave, other builds waiting for this build to complete, so entire CI system comes to a halt, followed by kaboom. And if nobody's looking, Jenkins will happily and shamelessly lock up your servers for days. So, why this happens? Surely, there's no single reason, but carefully selected assorti of toxic stuff: 1. Bugs in JVM/Java - just because there're comments above that switching to another JDK version/provider seem to alleviate it. 2. Bugs in Jenkins - just because every new release brings only security fixes as if previous version was something like 0.0.1, so you may imagine there's lot to fix yet. 3. But most importantly, that's the way Jenkins is written. To illustrate that, let's look at linked JENKINS-11586, comment straight from Kohsuke: "The ping currently is supposed to wait for 4 minutes before it gives up and kills the channel. But I have a hard time believing that the channel did really clog for 4 minutes." Here we go. Network over which that channel goes is UNRELIABLE. Everything you find hard to believe about it is actually true. It may fail to deliver stuff, it may clog for 4 or 40 minutes, RIAA may knock on your door telling you download forbidden torrents which you never did. Or take another example, straight from FastPipedInputStream.java as quoted in stacktrace above. In its header, it confesses to be java.io.PipedInputStream equivalent, which just "uses proper synchronization" and "doesn't rely on polling". A seasonal engineer would recognize smartness and forthlooking of Java engineers who did not trust Java to do synchronization and instead used strings-and-stick method. Now smart kids came who thought they could make it better, and now their code locks up servers throughout the world. Ok, enough intro to problem area. Let's look straight into FastPipedInputStream.java:175 which was caught red-handed in the stacktrace above: https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/FastPipedInputStream.java#L163 And what we see immediately is infinite loop. Just see yourself: it blocks in wait on buffer for 10s, then does some liveness checks (which, as we already learned, will fail to detect any issues regularly), the checks for updates from outside, and if nothing happens, it will hang there forever. Here it is, Jenkins coding style. Here's the patch: https://github.com/pfalcon/remoting/commit/239b3dcf26498ff296fabf770dffc7a456b2878c So, why am I writing all this? Over time, I learned that if people come to me with artifact archiving issues, the best thing I can suggest them is AVOID NATIVE JENKINS ARTIFACT ARCHIVING LIKE A PLAGUE. People listen, and that job whose stack trace is quoted above is no longer uses it (rest of our jobs didn't use it for years). So, while I hacked up the patch above, I don't really have sandbox to test it with. So, if you experience this issue, I encourage you to try that patch and share results. Just to clarify - the patch above is not going to fix this issue (if you want it not fail, then Java and Jenkins are wrong technologies). But instead it makes it fail fast and not waste the resources (it also addresses only one infinite loop, I'm sure there're dozens more). The stacktrace above happened with Jenins 1.532.1 on Linux/Ubuntu master/slave (x86, x64, arm slaves affected). Thanks for listening to the rant, and happy (or sour) Jenkinsing! This message is automatically generated by JIRA. If you think it was sent incorrectly,
[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Aswini Rajasekaran commented on JENKINS-7641 Slaves hang when archiving artifacts Hi, I just jenkins version 1.514 and this issues happens for me for the past 1 week. This is a big blocker for me in executing builds in slave. I have installed jenkins on linux box and all the slaves are also remote linux boxes connected via SSH. Can anyone advise how to resolve this at the earliest? Thanks a mil for your help in advance. Regards, Aswini 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Aswini Rajasekaran edited a comment on JENKINS-7641 Slaves hang when archiving artifacts Hi, I use jenkins version 1.514 and this issues happens for me for the past 1 week. This is a big blocker for me in executing builds in slave. I have installed jenkins on linux box and all the slaves are also remote linux boxes connected via SSH. Can anyone advise how to resolve this at the earliest? Thanks a mil for your help in advance. Regards, Aswini 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] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Oliver Bock commented on JENKINS-7641 Slaves hang when archiving artifacts This issue just got worse: with 1.502, when the build itself was successful, a failure to archive the artefacts did at least not change the overall build result to FAILURE. Unfortunately, with 1.511 it does: === Running test === Test passed === Archiving artifacts ERROR: Failed to archive artifacts: build.log hudson.util.IOException2: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at java.io.FilterInputStream.read(FilterInputStream.java:107) at hudson.util.HeadBufferingStream.fillSide(HeadBufferingStream.java:83) at hudson.FilePath$TarCompression$2.extract(FilePath.java:625) at hudson.FilePath.copyRecursiveTo(FilePath.java:1926) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.FilePath.copyRecursiveTo(FilePath.java:1933) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request$1.get(Request.java:278) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:1929) ... 10 more Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Build step 'Archive the artifacts' changed build result to FAILURE Finished: FAILURE 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
