[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Dilip M commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline See in: Core: Jenkins ver. 1.532.2 Build Pipeline Plugin: 1.4.3 Parameterized Trigger Plugin: 2.20 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
SCM/JIRA link daemon commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/CauseAction.java http://jenkins-ci.org/commit/jenkins/aa677ed8486559433ff71a50cf4f5bbf8fc46cd8 Log: JENKINS-20499 Don't fail horribly with null causes 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
SCM/JIRA link daemon commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/CauseAction.java http://jenkins-ci.org/commit/jenkins/0c76f85f8dd563963072323c68f25236d901a9ca Log: Merge pull request #1248 from daniel-beck/JENKINS-20499 JENKINS-20499 Don't fail horribly with null causes Compare: https://github.com/jenkinsci/jenkins/compare/b3bb235d5740...0c76f85f8dd5 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Oleg Nenashev updated JENKINS-20499 unable to retry job execution for failed job in build-pipeline marked as lts-candidate Change By: Oleg Nenashev (01/Jun/14 8:05 AM) Labels: lts-candidate 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
dogfood commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Integrated in jenkins_main_trunk #3417 JENKINS-20499 Don't fail horribly with null causes (Revision aa677ed8486559433ff71a50cf4f5bbf8fc46cd8) Result = SUCCESS daniel-beck : aa677ed8486559433ff71a50cf4f5bbf8fc46cd8 Files : core/src/main/java/hudson/model/CauseAction.java 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Daniel Beck commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Oleg: Better file a separate issue to make PR 1248 eligible for LTS. Oliver will never even see this unresolved issue for a different component. (And I still maintain this is a Build Pipeline bug, adding a null cause shouldn't 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/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Marcus Philip commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline A clue could be that since we upgraded the build pipeline plugin to 11088e6301 we ONLY see this happening on the first job in the pipeline. We have seen it hang on both SCM trigger and rebuild. Unsure if it ever happened on a plain manual trigger, but I don't think it has. We believe that it was the fix for JENKINS-21527 in 8ee1e7 (merged to mainline in 376b460e12) that fixed it. I think this is interesting because it highlights what was wrong and maybe a similar fix needs to be applied somewhere else. 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Marcus Philip edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline A clue could be that since we upgraded the build pipeline plugin to 11088e6301 we ONLY see this happening on the first job in the pipeline and never on downstream jobs like we saw before. We have seen it hang on both SCM trigger and rebuild. Unsure if it ever happened on a plain manual trigger, but I don't think it has. We believe that it was the fix for JENKINS-21527 in 8ee1e7 (merged to mainline in 376b460e12) that fixed it. I think this is interesting because it highlights what was wrong and maybe a similar fix needs to be applied somewhere else. 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Daniel Beck updated JENKINS-20499 unable to retry job execution for failed job in build-pipeline BuildPipelineView.triggerBuild(AbstractProject,AbstractBuild,Action) has a code path that leads to a null Cause being added to the CauseAction. Core cannot handle that. Change By: Daniel Beck (23/May/14 8:50 AM) 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/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Daniel Beck commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Could someone please provide clear step-by-step instructions on how yo reproduce the problem on a pristine Jenkins instance (be verbose, include the plugin installation and everythign!)? I tried David Fuenmayor's instructions, but they don't work for me (Jenkins 1.561, Build Pipeline 1.4.2). 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Ritvick Paliwal commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline I ran into same issue. Auto trigger from SCM without using"parameterized plugin". Any workaround for this ? How do I kill that build ? I even restarted jenkins but all in vain. Here is my stack track. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.560.jar!/hudson/model/CauseAction/summary.jelly:30:65: st:include No page found 'description.jelly' for class hudson.model.CauseAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Marcus Philip commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline We have seen this on a job triggered by a SCM change, so it does not seem to be related to build-pipeline plugin either. Jenkins: 1.525 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
ikedam updated JENKINS-20499 unable to retry job execution for failed job in build-pipeline From comments, this seems happen even without using parameterized trigger plugin. Removed parameterized-trigger from component/s. Change By: ikedam (20/Mar/14 11:59 PM) Component/s: parameterized-trigger 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Sagar Khanna commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline It works if you change the previous build to trigger the next build manually but doesn't if it an automatic trigger 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
cici thomson commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem: Ubuntu 12.04.4 LTS Jenkins: 1.551 Build Pipeline Plugin: 1.4.2 Not using Parameterized Triggers, but plugin 2.22 is installed for other projects 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Sagar Khanna commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same issue: CentOS release 6.4 Jenkins: 1.553 Build Pipeline Plugin: 1.4.2 Parameterized Trigger plugin: 2.22 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Ladislav Toldy commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem Jenkins: 1.532.2 Build Pipeline Plugin 1.4.2 But fixed after downgrading to Jenkins: 1.532.2 Build Pipeline Plugin 1.4 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Ladislav Toldy edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem Jenkins: 1.532.2 Build Pipeline Plugin 1.4.2 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Zachary Young commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same here Jenkins 1.550 Parameterized Trigger plugin 2.22 Build Pipeline Plugin 1.4.2 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Daniel Gonzalez commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem here Jenkins ver. 1.532.1 Parameterized Trigger plugin 2.22 Build Pipeline Plugin 1.4.2 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
David Fuenmayor commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline I am getting exactly the same problem and stacktrace (version 1.4.1 with Jenkins LTS 1.509.4) After triggering the same downstream project from two different upstream projects Steps to reproduce: 1. Create a downstream project D 2. Create Projects A and B. As post-build action select "Build Other Projects (manual step)" and select for both: Project D. Add some predefined parameters: (e.g MY_VAR = VALUE) 3. Create two Build Pipeline Views: One for Project A and one for Project B 4. Trigger downstream project D from Project A using its corresponding Build Pipeline View 5. Trigger downstream project D from Project B using its corresponding Build Pipeline View 6. Repeat 4 and 5 a couple of times. D runs broken and cannot be aborted 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
João Vale commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem here, with the same NullPointerException. CentOS 6.4 Jenkins 1.536 Build Pipeline 1.4.2 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Fabio Bazzani updated JENKINS-20499 unable to retry job execution for failed job in build-pipeline Change By: Fabio Bazzani (09/Nov/13 11:21 AM) Environment: OS LinuxRedHat6.3 ,Jenkinscore1.529,buildpipelineplugin1.4.2,parametrizedtriggerplugin2.21 Description: anewrunwithretrylinkonfailed the jobgetstuckwithoutanyoutputinconsole.logexception:Nov9,20131:04:34AMhudson.model.ExecutorrunSEVERE:Executorthrewanexceptionjava.lang.NullPointerExceptionathudson.model.CauseAction.onAttached(CauseAction.java:120)athudson.model.Run.addAction(Run.java:349)athudson.model.Executor.run(Executor.java:238)theruncannotbeabortedorcancelled.theonlywaytostopitisrestartingJenkins. 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-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Kyle Parker-Robinson commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline This repos on the following environment: Windows Server 2008 R2 Jenkins core 1.537 Build Pipeline plugin 1.4.1 Parametrized Trigger plugin 2.18 It occurs when a build is forced (Click "Build with Parameters", click "Build") after a failed build. 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.
