[JIRA] [template-project-plugin] (JENKINS-24404) Environment variables not exported with Use SCM from another project
SCM/JIRA link daemon resolved JENKINS-24404 as Fixed Environment variables not exported with Use SCM from another project Change By: SCM/JIRA link daemon (08/Apr/15 6:04 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [template-project-plugin] (JENKINS-24404) Environment variables not exported with Use SCM from another project
SCM/JIRA link daemon commented on JENKINS-24404 Environment variables not exported with Use SCM from another project Code changed in jenkins User: Brenton B Path: src/main/java/hudson/plugins/templateproject/ProxySCM.java http://jenkins-ci.org/commit/template-project-plugin/11bc1c8a59fa3b8bb5fe1fea9653225cd5c2db4c Log: Merge pull request #12 from vb-linetco/add-build-env-var-support FIXED JENKINS-24404 added support for build environment variables Compare: https://github.com/jenkinsci/template-project-plugin/compare/657f32764a92...11bc1c8a59fa 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] [role-strategy-plugin] (JENKINS-27829) authenticated user role is not working after saml integration
vishal sahasrabuddhe created JENKINS-27829 authenticated user role is not working after saml integration Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 08/Apr/15 6:30 AM Description: Hi, We had ldap integration and "authenticated" user bit was working fine to assign role for the logged in user. However after SAML integration for SSO, "authenticated" user role stopped working without throwing any error. Role based strategy plugin is working fine for individual users but it is not working for authenticated users. Project: Jenkins Labels: plugin Priority: Major Reporter: vishal sahasrabuddhe 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] [jobgenerator-plugin] (JENKINS-23215) Job generator deleting last generated job when slecting to delet any perticular job.
vishal sahasrabuddhe updated JENKINS-23215 Job generator deleting last generated job when slecting to delet any perticular job. Change By: vishal sahasrabuddhe (08/Apr/15 6:32 AM) Labels: plugins 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] [template-project-plugin] (JENKINS-15066) Long wait between last build step and first post build step
Brantone commented on JENKINS-15066 Long wait between last build step and first post build step This is going many years on, but @strand : did this fix resolve your issues? 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-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds @Arpit thanks for the feedback. It seems like there are objections to these changes in their current form (see the PR) so we might have to go back to the drawing board. I'm committed to a load of other work too (was doing this in spare 10 mins here and there) so, unless this is a big issue for you, we might have to put it on ice for a while until there's some sort of consensus (among the people that have the problem) re how best to address 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] [core] (JENKINS-27836) When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build.
dogfood commented on JENKINS-27836 When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build. Integrated in jenkins_main_trunk #4075 JENKINS-27836 Add test case (Revision 211df74765f35902028508ba104102d379d2) Result = SUCCESS stephen connolly : 211df74765f35902028508ba104102d379d2 Files : test/src/test/java/hudson/tasks/LogRotatorTest.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] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
dogfood commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Integrated in jenkins_main_trunk #4075 FIXED JENKINS-26520 Noting merge of #1637 (Revision 9fd4c1a854dfea43501060511cfd3597d83a0226) Result = SUCCESS stephen connolly : 9fd4c1a854dfea43501060511cfd3597d83a0226 Files : changelog.html 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] [artifactory-plugin] (JENKINS-27840) Bintray href anchor link in Jenkins invalid
Alexandru Gheorghe created JENKINS-27840 Bintray href anchor link in Jenkins invalid Issue Type: Bug Assignee: yossis Attachments: bintray.png Components: artifactory-plugin Created: 08/Apr/15 10:47 AM Description: Bintray publishing will link to https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin#ArtifactoryPlugin-PushToBintray instead of https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin#ArtifactoryPlugin-PushtoBintray Please also see attached screenshot. Environment: awt.toolkit sun.awt.X11.XToolkit executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-7-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_65-b32 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_65 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.65-b04 jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna107757935724408517.tmp lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate lib.svnkit.ssh2.persistent false line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.13.0-36-generic path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/classes sun.boot.library.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Europe/Rome Project: Jenkins Priority: Trivial Reporter: Alexandru Gheorghe This message is automatically
[JIRA] [github-oauth-plugin] (JENKINS-27843) Exception when enabling Use Github repository permissions
Leandro Lucarella created JENKINS-27843 Exception when enabling Use Github repository permissions Issue Type: Bug Assignee: Sam Kottler Attachments: j.png Components: github-oauth-plugin Created: 08/Apr/15 11:43 AM Description: I get this exception when enabling the "Use Github repository permissions" option for any non-admin user in the main page. Job result pages seem to work. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.596.2.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include java.lang.NullPointerException 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:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [groovy-plugin] (JENKINS-27834) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur commented on JENKINS-27834 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Closing the ticket as it is duplicate of JENKINS-27833 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Hi, BSIM is a product with testcases and CDB is the job running the testcases. My issue is this groovy problem has come up in other builds too. I'm unable to figure out the cause of it. Regards, Judah 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB K you can close the ticket. Thanks for the help. 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] [template-project-plugin] (JENKINS-23204) Template Plugin to be able to import job parameters
Tom Ghyselinck commented on JENKINS-23204 Template Plugin to be able to import job parameters Hi Brantone, Thank you very much for looking into this! We need this functionality more and more. I would use this as follows: We have a Template Job name "TemplateJob" This Job defines parameter "PARAMETER1", "PARAMETER2" and "PARAMETER3" We have several Jobs, name MyJob1, MyJob2, MyJob3, ... All of these Jobs use "TemplateJob" These Jobs import one or more of the parameters from the template job. I suggest the most flexible way to use the parameters from the "TemplateJob" (in e.g. "MyJob1") is: Select "This build is parameterised" "Add Parameter" - "Use parameter from another Job" (this would be the new part) "Select" parameter name When performing a manual build, I suggest it should be possible to obtain all required parameter info from the "TemplateJob" configuration. (We should see the same parameter info as when the parameters would be configured in "MyJob1" directly) Note: One difficult part may be recursion: Suppose we have: Template Job "TemplateJob1" and "TemplateJob2" These are simple template jobs "TemplateJob1" defines parameter "PARAMETER11", "PARAMETER12" and "PARAMETER13" "TemplateJob2" defines parameter "PARAMETER21", "PARAMETER22" and "PARAMETER23" Template Job "TemplateJobX" This Job uses parameters, build steps, post build steps, etc. from "TemplateJob1" and "TemplateJob2" E.g. Using parameters "PARAMETER11" and "PARAMETER12" from "TemplateJob1" E.g. Using parameters "PARAMETER22" and "PARAMETER23" from "TemplateJob2" Actual main Job "MyJob1" Using parameters from "TemplateJobX" E.g. Using parameters "PARAMETER11" and "PARAMETER12" from "TemplateJobX" (which actually came from "TemplateJob1") E.g. Using parameters "PARAMETER22" from "TemplateJobX" (which actually came from from "TemplateJob2") E.g. Additionally using parameter "PARAMETER13" from "TemplateJob1" If this is too complex too implement, it can be simplified: Template Job configuration same as shown above. Actual main Job "MyJob1" E.g. (Directly) using parameters "PARAMETER11", "PARAMETER12" and "PARAMETER13" from "TemplateJob1" E.g. (Directly) using parameters "PARAMETER22" and "PARAMETER23" from "TemplateJob2" I hope this helps you figuring out the design. with best regards, Tom. 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] [veracode-scanner-plugin] (JENKINS-27823) error while Configuring a Jenkins Job for Veracode Analysis
kineret amor
updated JENKINS-27823
error while Configuring a Jenkins Job for Veracode Analysis
Change By:
kineret amor
(08/Apr/15 9:59 AM)
Description:
Hey,iwanttoconfigureaJenkinsJobforVeracodeAnalysisiuseexistsjenkinsjoband
addthe
addthe
configurationforveracodeandigeterror:{code}javax.servlet.ServletException:java.lang.RuntimeException:Failedtoinstantiateclasscom.veracode.jenkins.plugin.VeracodeNotifierfrom{appname:eWXifPNJvV55cuKUu3RSnREtsoDevgYewDos3jtwMAg=,createprofile:false,criticality:EyfMO+rq6E+xW66bF+ATElZqV96tr36ltWm1DFSfZ1Q=,sandboxname:r6dVQWb0hvPfPhVYTVTCsw==,createsandbox:false,version:YsBsaurW4vLBgjko+uucfxEtsoDevgYewDos3jtwMAg=,uploadincludespattern:bDDj/V3GHLT8UbeMoISTYLcbo+yPWQY6PJWMaom8VLA=,uploadexcludespattern:r6dVQWb0hvPfPhVYTVTCsw==,scanincludespattern:r6dVQWb0hvPfPhVYTVTCsw==,scanexcludespattern:r6dVQWb0hvPfPhVYTVTCsw==,filenamepattern:r6dVQWb0hvPfPhVYTVTCsw==,replacementpattern:r6dVQWb0hvPfPhVYTVTCsw==,credentials:{vuser:CCX2RD+bn1Dd0JhwSapj+FePR5gurmHqCtiTsawx0xcdDKPT7MWdRL+xTGPQfgt9,vpassword:Ki5HSB0Nj6qJRwubRxQllB0ib7JWCDe+CD4dZ2mSXAY=},stapler-class:com.veracode.jenkins.plugin.VeracodeNotifier,kind:com.veracode.jenkins.plugin.VeracodeNotifier,$class:vvhrZXx9/XAtMIZ89EIg7ucGQfVOYuljjvwB+X5HHnNghkYPMCSg85kie6zfQz6GES2ygN6+Bh7AOizeO3AwCA==} atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) atorg.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
[JIRA] [subversion-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman commented on JENKINS-27620 SCM polling broken for servers with variable in path Actually, now that i'm looking a bit further, it seem that the real problem is that SCM polling isn't able to find the credentials anymore. This information is in the SCM polling log, and not in the Jenkins master log. Manually triggering the build, SVN has no problem finding the credentials. 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-11396) Cannot add Build Steps from UI of FreeStyle jobs
centic commented on JENKINS-11396 Cannot add Build Steps from UI of FreeStyle jobs @Larry: For me it happens when I somehow mix up http and https Jenkins URLs. I usually have https everywhere via an Apache Proxy, but sometimes end up on a http-one. There I see this error 404 with $stapler in the URL. Going to the https-page solves it, I just need to find out where there is still some http-reference stored on my machine 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] [workflow-plugin] (JENKINS-25550) Hard kill
Christoph Vogtländer commented on JENKINS-25550 Hard kill I'm not able to stop the build using the workaround: java.io.IOException: D:\Jenkins\jobs\job\builds\2015-04-05_00-41-16 is in use at hudson.model.Run.delete(Run.java:1523) at hudson.model.Run.doDoDelete(Run.java:2193) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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 jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) at com.marvelution.jenkins.plugins.jira.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.OAuthFilter.doFilter(OAuthFilter.java:87) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [workflow-plugin] (JENKINS-25550) Hard kill
Christoph Vogtländer edited a comment on JENKINS-25550 Hard kill I'm not able to stop the build using the workaround: java.io.IOException: D:\Jenkins\jobs\job\builds\2015-04-05_00-41-16 is in use at hudson.model.Run.delete(Run.java:1523) at hudson.model.Run.doDoDelete(Run.java:2193) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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 jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) at com.marvelution.jenkins.plugins.jira.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.OAuthFilter.doFilter(OAuthFilter.java:87) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [github-plugin] (JENKINS-27842) Support webhook events from github
Pedro Algarvio created JENKINS-27842 Support webhook events from github Issue Type: Improvement Assignee: Unassigned Components: github-plugin Created: 08/Apr/15 11:29 AM Description: I'd like to have some jobs triggered when pull requests are opened/closed and when new branches are created/deleted. Additionally, I'd also like to setup a push webhook, I know I could use the existing push trigger but this uses the github jenkins hook "app" which can only trigger one instance at a time and we have a testing/staging/production setup. My guess is that the best way to do all of this would be to let the user select which events the job would react to by having a general webhook trigger. Project: Jenkins Priority: Minor Reporter: Pedro Algarvio 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-11396) Cannot add Build Steps from UI of FreeStyle jobs
centic commented on JENKINS-11396 Cannot add Build Steps from UI of FreeStyle jobs The mixup of http/https in my case seems to be caused by JENKINS-10675, setting header X-Forwarded-Proto on the Apache proxy made it work 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Dominique Brice commented on JENKINS-27588 Labels used in Label Factory are shown as not used dev release available for test. 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] [artifactory-plugin] (JENKINS-27840) Bintray href anchor link in Jenkins invalid
Alexandru Gheorghe updated JENKINS-27840 Bintray href anchor link in Jenkins invalid Change By: Alexandru Gheorghe (08/Apr/15 10:50 AM) Environment: Jenkinsv1.607Artifactoryv2.3.0 awt.toolkit sun.awt.X11.XToolkitexecutable-war /usr/share/jenkins/jenkins.warfile.encoding UTF-8file.encoding.pkg sun.iofile.separator /hudson.diyChunking truejava.awt.graphicsenv sun.awt.X11GraphicsEnvironmentjava.awt.headless truejava.awt.printerjob sun.print.PSPrinterJobjava.class.path /usr/share/jenkins/jenkins.warjava.class.version 51.0java.endorsed.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/endorsedjava.ext.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/extjava.home /usr/lib/jvm/java-7-openjdk-amd64/jrejava.io.tmpdir /tmpjava.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/libjava.runtime.name OpenJDKRuntimeEnvironmentjava.runtime.version 1.7.0_65-b32java.specification.name JavaPlatformAPISpecificationjava.specification.vendor OracleCorporationjava.specification.version 1.7java.vendor OracleCorporationjava.vendor.url http://java.oracle.com/java.vendor.url.bug http://bugreport.sun.com/bugreport/java.version 1.7.0_65java.vm.info mixedmodejava.vm.name OpenJDK64-BitServerVMjava.vm.specification.name JavaVirtualMachineSpecificationjava.vm.specification.vendor OracleCorporationjava.vm.specification.version 1.7java.vm.vendor OracleCorporationjava.vm.version 24.65-b04jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/libjnidispatch.path /tmp/jna--1712433994/jna107757935724408517.tmplib.svnkit.http.methods Digest,Basic,NTLM,Negotiatelib.svnkit.ssh2.persistent falseline.separator mail.smtp.sendpartial truemail.smtps.sendpartial trueos.arch amd64os.name Linuxos.version 3.13.0-36-genericpath.separator :sun.arch.data.model 64sun.boot.class.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/classessun.boot.library.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64sun.cpu.endian littlesun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManagersun.io.unicode.encoding UnicodeLittlesun.java.command /usr/share/jenkins/jenkins.war--webroot=/var/cache/jenkins/war--httpPort=8080--ajp13Port=-1sun.java.launcher SUN_STANDARDsun.jnu.encoding UTF-8sun.management.compiler HotSpot64-BitTieredCompilerssun.os.patch.level unknownuser.country USuser.dir /user.home /var/lib/jenkinsuser.language enuser.name jenkinsuser.timezone Europe/Rome 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-failure-analyzer-plugin] (JENKINS-27841) Cannot connect to MongoDB
Per Östman created JENKINS-27841 Cannot connect to MongoDB Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 08/Apr/15 11:26 AM Description: Repro steps: Installed latest Mongo DB (3.0.1) Configured BFA to use MongoDB using correct credentials (verified URL, port credentials using the Mongo client tool) Pressed "Test Connection" Result: Could not connect javax.naming.AuthenticationException: Could not athenticate with the mongo database at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase.getDb(MongoDBKnowledgeBase.java:1080) at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase.getCollection(MongoDBKnowledgeBase.java:1094) at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase.access$000(MongoDBKnowledgeBase.java:90) at com.sonyericsson.jenkins.plugins.bfa.db.MongoDBKnowledgeBase$MongoDBKnowledgeBaseDescriptor.doTestConnection(MongoDBKnowledgeBase.java:1235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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:123) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:43) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at
[JIRA] [github-oauth-plugin] (JENKINS-27844) Improve Use Github repository permissions
Leandro Lucarella created JENKINS-27844 Improve Use Github repository permissions Issue Type: Bug Assignee: Sam Kottler Components: github-oauth-plugin Created: 08/Apr/15 11:48 AM Description: The current option "Use Github repository permissions" says: If checked will use github repository permissions to determine jenkins permissions for each project. Public projects - all authenticated users can READ. Only collaborators can BUILD, EDIT, CONFIGURE or DELETE. Private projects, only collaborators can READ, BUILD, EDIT, CONFIGURE or DELETE For private repos there are 3 access levels: pull (read) access, push (write) access and admin access. It would be much better to give people will pull access READ permission, people with push access READ/BUILD permission and READ, BUILD, EDIT, CONFIGURE or DELETE only to admins. Environment: Jenkins ver. 1.596.2, Ubuntu 12.04 Project: Jenkins Priority: Minor Reporter: Leandro Lucarella 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] [veracode-scanner-plugin] (JENKINS-27823) error while Configuring a Jenkins Job for Veracode Analysis
kineret amor
updated JENKINS-27823
error while Configuring a Jenkins Job for Veracode Analysis
Change By:
kineret amor
(08/Apr/15 10:06 AM)
Description:
Hey,iwanttoconfigureaJenkinsJobforVeracodeAnalysisiuseexistsjenkinsjobandaddtheconfigurationforveracodeandigeterror:{code}javax.servlet.ServletException:java.lang.RuntimeException:Failedtoinstantiateclasscom.veracode.jenkins.plugin.VeracodeNotifierfrom{appname:eWXifPNJvV55cuKUu3RSnREtsoDevgYewDos3jtwMAg=,createprofile:false,criticality:EyfMO+rq6E+xW66bF+ATElZqV96tr36ltWm1DFSfZ1Q=,sandboxname:r6dVQWb0hvPfPhVYTVTCsw==,createsandbox:false,version:YsBsaurW4vLBgjko+uucfxEtsoDevgYewDos3jtwMAg=,uploadincludespattern:bDDj/V3GHLT8UbeMoISTYLcbo+yPWQY6PJWMaom8VLA=,uploadexcludespattern:r6dVQWb0hvPfPhVYTVTCsw==,scanincludespattern:r6dVQWb0hvPfPhVYTVTCsw==,scanexcludespattern:r6dVQWb0hvPfPhVYTVTCsw==,filenamepattern:r6dVQWb0hvPfPhVYTVTCsw==,replacementpattern:r6dVQWb0hvPfPhVYTVTCsw==,credentials:{vuser:CCX2RD+bn1Dd0JhwSapj+FePR5gurmHqCtiTsawx0xcdDKPT7MWdRL+xTGPQfgt9,vpassword:
Ki5HSB0Nj6qJRwubRxQllB0ib7JWCDe
tD684Mcd7F9C6XPEkllLZB0Mo9PsxZ1Ev7FMY9B
+
CD4dZ2mSXAY
C30
=},stapler-class:com.veracode.jenkins.plugin.VeracodeNotifier,kind:com.veracode.jenkins.plugin.VeracodeNotifier,$class:vvhrZXx9/XAtMIZ89EIg7ucGQfVOYuljjvwB+X5HHnNghkYPMCSg85kie6zfQz6GES2ygN6+Bh7AOizeO3AwCA==} atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) atorg.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
[JIRA] [allure-plugin] (JENKINS-27839) Allure report generation failure
Judah Benhur created JENKINS-27839 Allure report generation failure Issue Type: Bug Assignee: Artem Eroshenko Components: allure-plugin Created: 08/Apr/15 10:33 AM Description: Hi, ERROR: Publisher ru.yandex.qatools.allure.jenkins.AllureReportPublisher aborted due to exception java.io.IOException: remote file operation failed: /home/ossrcdm/jenkins/workspace/GRAN_BSM_KGB_AAT_16.0/allure3631959284172426911.tmp at hudson.remoting.Channel@58278a71:Jenkins_CI_7 at hudson.FilePath.act(FilePath.java:910) at hudson.FilePath.act(FilePath.java:887) at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.generateReport(AllureReportPublisher.java:243) at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.perform(AllureReportPublisher.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663) at hudson.model.Run.execute(Run.java:1713) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: ru.yandex.qatools.allure.report.AllureReportBuilderException: java.lang.NullPointerException at ru.yandex.qatools.allure.jenkins.utils.ReportGenerator.invoke(ReportGenerator.java:50) at ru.yandex.qatools.allure.jenkins.utils.ReportGenerator.invoke(ReportGenerator.java:25) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2462) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: ru.yandex.qatools.allure.report.AllureReportBuilderException: java.lang.NullPointerException at ru.yandex.qatools.allure.report.AllureReportBuilder.processResults(AllureReportBuilder.java:133) at ru.yandex.qatools.allure.jenkins.utils.ReportGenerator.invoke(ReportGenerator.java:47) ... 11 more Caused by: java.lang.NullPointerException at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:361) at ru.yandex.qatools.clay.Aether.resolveWithTransitives(Aether.java:177) at ru.yandex.qatools.clay.Aether.resolve(Aether.java:131) at ru.yandex.qatools.clay.Aether.resolve(Aether.java:109) at ru.yandex.qatools.allure.report.AllureReportBuilder.processResults(AllureReportBuilder.java:127) ... 12 more Can you please look into this issue? Regards and thanks in advance, Judah Project: Jenkins Priority: Major Reporter: Judah Benhur 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
[JIRA] [template-project-plugin] (JENKINS-23204) Template Plugin to be able to import job parameters
Brantone commented on JENKINS-23204 Template Plugin to be able to import job parameters Actually ... is this intended for (a.) the template project to import params itself? -- I would think that'd become a confusing subset. (b.) the template project to use the params from the calling project? -- I believe it already does that. (c.) ??? 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] [template-project-plugin] (JENKINS-16800) When including publishers from another job, the link to the report is not added
Brantone closed JENKINS-16800 as Fixed When including publishers from another job, the link to the report is not added Change By: Brantone (08/Apr/15 7:42 AM) 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] [groovy-plugin] (JENKINS-27834) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur created JENKINS-27834 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 08/Apr/15 8:27 AM Description: BSIM Test Cases in CDB are failing as Groovy-All bundle is not deployed while preparing the Test. So, the Groovy scripts are not able to register and all the test cases are skipped. This issue is intermittently seen on CDB server. Please find below the link to console output for CDB run on three consecutive times. In two of these, the issue is seen. Latest CDB Console Logs where this issue is seen: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/131/consoleFull CDB Console Logs where Groovy-All was successfully deployed: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/130/consoleFull CDB Console Logs where this issue is seen: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/124/consoleFull Please note that this issue is not seen in BSIM KGB and Groovy-All is successfully deployed. Latest KGB Report: https://jenkins.lmera.ericsson.se/auto/job/1_BSIM_TAF_KGB_NIGHTLY_BUILD_15/313/allure/#/home Project: Jenkins Priority: Blocker Reporter: Judah Benhur 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur created JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 08/Apr/15 8:26 AM Description: BSIM Test Cases in CDB are failing as Groovy-All bundle is not deployed while preparing the Test. So, the Groovy scripts are not able to register and all the test cases are skipped. This issue is intermittently seen on CDB server. Please find below the link to console output for CDB run on three consecutive times. In two of these, the issue is seen. Latest CDB Console Logs where this issue is seen: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/131/consoleFull CDB Console Logs where Groovy-All was successfully deployed: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/130/consoleFull CDB Console Logs where this issue is seen: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/124/consoleFull Please note that this issue is not seen in BSIM KGB and Groovy-All is successfully deployed. Latest KGB Report: https://jenkins.lmera.ericsson.se/auto/job/1_BSIM_TAF_KGB_NIGHTLY_BUILD_15/313/allure/#/home Project: Jenkins Priority: Blocker Reporter: Judah Benhur 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-27836) When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build.
SCM/JIRA link daemon resolved JENKINS-27836 as Fixed When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build. Change By: SCM/JIRA link daemon (08/Apr/15 8:46 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Hi, Exception: - 2015-04-07 09:36:36,352 BSIM CDB Suite DEBUG com.ericsson.cifwk.taf.osgi.client.OsgiContainerHandler Checking 424ACTIVE groovy-all_2.1.9 for Bundle Number java.lang.NullPointerException at org.eclipse.core.runtime.internal.adaptor.CachedManifest.keys(CachedManifest.java:64) at org.eclipse.osgi.framework.internal.core.ManifestLocalization.getHeaders(ManifestLocalization.java:57) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getHeaders(AbstractBundle.java:950) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getHeaders(AbstractBundle.java:897) at org.eclipse.osgi.framework.internal.core.AbstractBundle.uninstallWorkerPrivileged(AbstractBundle.java:819) at org.eclipse.osgi.framework.internal.core.AbstractBundle$4.run(AbstractBundle.java:766) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.AbstractBundle.uninstallWorker(AbstractBundle.java:790) at org.eclipse.osgi.framework.internal.core.AbstractBundle.uninstall(AbstractBundle.java:764) at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._uninstall(FrameworkCommandProvider.java:413) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224) at java.lang.Thread.run(Thread.java:745) osgi 2015-04-07 09:36:36,488 BSIM CDB Suite DEBUG com.ericsson.cifwk.taf.osgi.client.OsgiContainerHandler Response from expect is: java.lang.NullPointerException at org.eclipse.core.runtime.internal.adaptor.CachedManifest.keys(CachedManifest.java:64) at org.eclipse.osgi.framework.internal.core.ManifestLocalization.getHeaders(ManifestLocalization.java:57) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getHeaders(AbstractBundle.java:950) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getHeaders(AbstractBundle.java:897) at org.eclipse.osgi.framework.internal.core.AbstractBundle.uninstallWorkerPrivileged(AbstractBundle.java:819) at org.eclipse.osgi.framework.internal.core.AbstractBundle$4.run(AbstractBundle.java:766) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.AbstractBundle.uninstallWorker(AbstractBundle.java:790) at org.eclipse.osgi.framework.internal.core.AbstractBundle.uninstall(AbstractBundle.java:764) at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._uninstall(FrameworkCommandProvider.java:413) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224) at java.lang.Thread.run(Thread.java:745) osgi 2015-04-07 09:36:36,492 BSIM CDB Suite INFO com.ericsson.cifwk.taf.osgi.client.OsgiContainerClient Attempting to deploy groovy-all bundle org.eclipse.osgi.framework.internal.core.Framework$DuplicateBundleException: Bundle "groovy-all" version "2.1.9" has already been installed from: file:///tmp/groovy-all.jar at org.eclipse.osgi.framework.internal.core.Framework.createAndVerifyBundle(Framework.java:709) at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:923) at org.eclipse.osgi.framework.internal.core.Framework$1.run(Framework.java:838) at
[JIRA] [core] (JENKINS-27836) When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build.
SCM/JIRA link daemon commented on JENKINS-27836 When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build. Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/6e7e3c8f3ae7fd048ab34a4eb3469d89679d6949 Log: FIXED JENKINS-27836 Noting merge of #1570 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-27571) Workflow Job: Back to Project link not navigating
Daniel Beck updated JENKINS-27571 Workflow Job: Back to Project link not navigating Change By: Daniel Beck (08/Apr/15 9:35 AM) Assignee: JesseGlick Component/s: workflow-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] [scm-sync-configuration-plugin] (JENKINS-27830) scm sync configuration checkout problem
parvez alam updated JENKINS-27830 scm sync configuration checkout problem Change By: parvez alam (08/Apr/15 7:33 AM) Description: Hi,Iamnewbyinjenkins,Iwanttocreatebackupongithub husing using scmsyncplugin,Ihavefollowfollowingsteps.1-IhavesetgitglobalcredentialsintojenkinsGIToptionunderjenkinsconfiguresystem-GIT.2-Installedscmsyncpluginandputconfigurationparameterinjenkinsscmsyncconfigurationtabandsetrepourlg...@github.com:username/jenkins_config.git3-saveButIamgettingbelowerror:Thegit-clonecommandfailed.||fatal:destinationpath/usr/share/tomcat7/.jenkins/scm-sync-configuration/checkoutConfigurationalreadyexistsandisnotanemptydirectory. 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] [template-project-plugin] (JENKINS-27831) Better try-catch around `getProject()`
Brantone created JENKINS-27831 Better try-catch around `getProject()` Issue Type: Bug Assignee: huybrechts Components: template-project-plugin Created: 08/Apr/15 7:34 AM Description: In the case of : src/java/hudson/plugins/templateproject/ProxyBuilder.java - getProjectBuilders() src/java/hudson/plugins/templateproject/ProxySCM.java - getProject() src/java/hudson/plugins/templateproject/ProxyPublisher.java - getProject() Need to have proper try-catch, such that outputs proper error message instead of throwing NPE or silent fail (as sometimes happens with Folder plugin). Project: Jenkins Priority: Major Reporter: Brantone 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] [scm-sync-configuration-plugin] (JENKINS-27830) scm sync configuration checkout problem
parvez alam created JENKINS-27830 scm sync configuration checkout problem Issue Type: Task Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 08/Apr/15 7:33 AM Description: Hi, I am newby in jenkins,I want to create backup on github husing scm sync plugin,I have follow following steps. 1- I have set git global credentials into jenkins GIT option under jenkins configure system-GIT. 2- Installed scm sync plugin and put configuration parameter in jenkins scm sync configuration tab and set repo url g...@github.com:username/jenkins_config.git 3 - save But I am getting below error: The git-clone command failed. || fatal: destination path '/usr/share/tomcat7/.jenkins/scm-sync-configuration/checkoutConfiguration' already exists and is not an empty directory. Environment: linux Project: Jenkins Priority: Critical Reporter: parvez alam 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] [template-project-plugin] (JENKINS-27831) Better try-catch around `getProject()`
Brantone updated JENKINS-27831 Better try-catch around `getProject()` Change By: Brantone (08/Apr/15 7:39 AM) Issue Type: Bug Improvement Description: Inthecaseof:*src/ main/ java/hudson/plugins/templateproject/ProxyBuilder.java-getProjectBuilders()*src/ main/ java/hudson/plugins/templateproject/ProxySCM.java-getProject()*src/ main/ java/hudson/plugins/templateproject/ProxyPublisher.java-getProject()Needtohavepropertry-catch,suchthatoutputspropererrormessageinsteadofthrowingNPEorsilentfail(assometimeshappenswithFolderplugin). 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] [job-dsl-plugin] (JENKINS-27832) Allow configuration of build after other projects trigger
Mark Syms created JENKINS-27832 Allow configuration of build after other projects trigger Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 08/Apr/15 8:22 AM Description: Since Jenkins 1.560 it has been possible to configure a project to "Build after other projects are built". The DSL does not currently support this form of trigger which allows the downstream job to start independently of the upstream job rather than running as a sub task. I have an implementation, pull request will be following. Environment: Jenkins: 1.605 Project: Jenkins Priority: Minor Reporter: Mark Syms 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] [groovy-plugin] (JENKINS-27835) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur closed JENKINS-27835 as Duplicate Groovy-All Bundle not deployed for BSIM Test Cases in CDB Duplicate of JENKINS-27833 Change By: Judah Benhur (08/Apr/15 8:39 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] [groovy-plugin] (JENKINS-27834) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur closed JENKINS-27834 as Duplicate Groovy-All Bundle not deployed for BSIM Test Cases in CDB Duplicate of JENKINS-27833 Change By: Judah Benhur (08/Apr/15 8:39 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] [veracode-scanner-plugin] (JENKINS-27823) error while Configuring a Jenkins Job for Veracode Analysis
kineret amor
updated JENKINS-27823
error while Configuring a Jenkins Job for Veracode Analysis
Change By:
kineret amor
(08/Apr/15 9:50 AM)
Description:
Hey,iwanttoconfigureaJenkinsJobforVeracodeAnalysis
iuseexistsjenkinsjob
and
addtheconfigurationforveracodeand
igeterror:{code}javax.servlet.ServletException:java.lang.RuntimeException:Failedtoinstantiateclasscom.veracode.jenkins.plugin.VeracodeNotifierfrom{appname:
HgBpbe/yHpIRMZ7PINv05K+nVUFm9Ibz3z4VWE1UwrM
eWXifPNJvV55cuKUu3RSnREtsoDevgYewDos3jtwMAg
=,createprofile:
true
false
,criticality:EyfMO+rq6E+xW66bF+ATElZqV96tr36ltWm1DFSfZ1Q=,sandboxname:r6dVQWb0hvPfPhVYTVTCsw==,createsandbox:false,version:
emw4tq5QUPrFKrnBzlgyJiIhypRFRgvRqozr1cAIPJo
YsBsaurW4vLBgjko+uucfxEtsoDevgYewDos3jtwMAg
=,uploadincludespattern:bDDj/V3GHLT8UbeMoISTYLcbo+yPWQY6PJWMaom8VLA=,uploadexcludespattern:r6dVQWb0hvPfPhVYTVTCsw==,scanincludespattern:r6dVQWb0hvPfPhVYTVTCsw==,scanexcludespattern:r6dVQWb0hvPfPhVYTVTCsw==,filenamepattern:
PGaSiDnCGlAQeUJAOtD3ka+nVUFm9Ibz3z4VWE1UwrM
r6dVQWb0hvPfPhVYTVTCsw
=
=
,replacementpattern:
j0awvuMa5UvPW8Zl78snddYIkdPxiXqG6umKs27fcMJ3FkW1fiOi+z76PDlOW5VO
r6dVQWb0hvPfPhVYTVTCsw==
,credentials:{vuser:CCX2RD+bn1Dd0JhwSapj+FePR5gurmHqCtiTsawx0xcdDKPT7MWdRL+xTGPQfgt9,vpassword:
tD684Mcd7F9C6XPEkllLZB0Mo9PsxZ1Ev7FMY9B
Ki5HSB0Nj6qJRwubRxQllB0ib7JWCDe
+
C30
CD4dZ2mSXAY
=},stapler-class:com.veracode.jenkins.plugin.VeracodeNotifier,kind:com.veracode.jenkins.plugin.VeracodeNotifier,$class:vvhrZXx9/XAtMIZ89EIg7ucGQfVOYuljjvwB+X5HHnNghkYPMCSg85kie6zfQz6GES2ygN6+Bh7AOizeO3AwCA==} atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
[JIRA] [role-strategy-plugin] (JENKINS-27829) authenticated user role is not working after saml integration
Oleg Nenashev commented on JENKINS-27829 authenticated user role is not working after saml integration Please follow the guides on https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue An info about Jenkins core and SSO plugin versions is required 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] [role-strategy-plugin] (JENKINS-27829) authenticated user role is not working after saml integration
Oleg Nenashev edited a comment on JENKINS-27829 authenticated user role is not working after saml integration Please follow the guide on https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue An info about Jenkins core and SSO plugin versions is required 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
vjuranek commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Skimming through the exception, it looks like it has nothing to do with Jenkins groovy plugin. Basically your custom framework fails to load groovy jar via OSGi - so probably some misconfiguration of your OSGi bundles or something like this. I'm afraid I cannot help here, it seems to be some issue in your internal framework. 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] [job-dsl-plugin] (JENKINS-27838) Allow CopyArtifacts command to specify excludes filter
Mark Syms created JENKINS-27838 Allow CopyArtifacts command to specify excludes filter Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 08/Apr/15 9:28 AM Description: The CopyArtifact command does not allow an exclude filter to be specified which requires all artefacts matching an include filter to be copied to the downstream job. This is quite inflexible when there may be several downstream test jobs requiring different subsets of build outputs. I have an implementation, pull request to follow. Project: Jenkins Priority: Minor Reporter: Mark Syms 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] [other] (JENKINS-27423) User ID is non-sensical using saml-plugin
Daniel Beck updated JENKINS-27423 User ID is non-sensical using saml-plugin Change By: Daniel Beck (08/Apr/15 9:37 AM) Component/s: other 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
vjuranek resolved JENKINS-27833 as Not A Defect Groovy-All Bundle not deployed for BSIM Test Cases in CDB Change By: vjuranek (08/Apr/15 9:37 AM) 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB BSIM team has their own job where the job get success, but CDB job where other products are combined and run, the above log comes up. Can you help me understand why this issue is caused and what can be done to avoid this error. Regards, Judah 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-27836) When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build.
SCM/JIRA link daemon commented on JENKINS-27836 When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build. Code changed in jenkins User: Stephen Connolly Path: test/src/test/java/hudson/tasks/LogRotatorTest.java http://jenkins-ci.org/commit/jenkins/211df74765f35902028508ba104102d379d2 Log: JENKINS-27836 Add test case Compare: https://github.com/jenkinsci/jenkins/compare/6e7e3c8f3ae7...211df747 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
SCM/JIRA link daemon commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/9fd4c1a854dfea43501060511cfd3597d83a0226 Log: FIXED JENKINS-26520 Noting merge of #1637 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] [template-project-plugin] (JENKINS-16800) When including publishers from another job, the link to the report is not added
Brantone resolved JENKINS-16800 as Fixed When including publishers from another job, the link to the report is not added Fixed with merge PR https://github.com/jenkinsci/template-project-plugin/pull/5 Change By: Brantone (08/Apr/15 7:40 AM) Status: Open Resolved Assignee: huybrechts 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] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Daniel Spilker commented on JENKINS-27826 Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test Which coreVersion did you set in the build file? Only core versions 1.420 or later are supported, so adding a dependency to an ancient core version is not helping. As of Jenkins 1.561 the Matrix project has been moved to a plugin outside of Jenkins core, so you might need to add a dependency to that plugin. https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+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] [groovy-plugin] (JENKINS-27835) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
Judah Benhur created JENKINS-27835 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 08/Apr/15 8:29 AM Description: BSIM Test Cases in CDB are failing as Groovy-All bundle is not deployed while preparing the Test. So, the Groovy scripts are not able to register and all the test cases are skipped. This issue is intermittently seen on CDB server. Please find below the link to console output for CDB run on three consecutive times. In two of these, the issue is seen. Latest CDB Console Logs where this issue is seen: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/131/consoleFull CDB Console Logs where Groovy-All was successfully deployed: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/130/consoleFull CDB Console Logs where this issue is seen: https://jenkins.lmera.ericsson.se/ossrc-cdb/job/Cloud_CDB_Auto_Deployment_EU_Upgrade/124/consoleFull Please note that this issue is not seen in BSIM KGB and Groovy-All is successfully deployed. Latest KGB Report: https://jenkins.lmera.ericsson.se/auto/job/1_BSIM_TAF_KGB_NIGHTLY_BUILD_15/313/allure/#/home Project: Jenkins Priority: Blocker Reporter: Judah Benhur 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Thanks Tom i added my 2c to the pull request. Lets see if that helps . 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] [template-project-plugin] (JENKINS-22381) The plugin do not fail the build if a template is removed
Brantone commented on JENKINS-22381 The plugin do not fail the build if a template is removed The issue is more than just ProxyBuilder but also ProxySCM + ProxyPublisher. Thus created https://issues.jenkins-ci.org/browse/JENKINS-27831 to encompass them all 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] [role-strategy-plugin] (JENKINS-27829) authenticated user role is not working after saml integration
vishal sahasrabuddhe commented on JENKINS-27829 authenticated user role is not working after saml integration Hi Oleg, Sorry for incomplete information. Following is the detail information Jenkins version - 1.5.80.3 Role bases strategy plugin version - 2.2.0 SAML Plugin version - 0.3 OS - ubuntu 10.04 jenkins is running as service from its war. We have checked our SAML server which are working without issue for 8-10 other services, so i can say no issue from SSO server side. 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] [template-project-plugin] (JENKINS-15861) SCMTrigger runs with anonymous authentication
Brantone commented on JENKINS-15861 SCMTrigger runs with anonymous authentication I wonder if this is fixed by https://github.com/jenkinsci/template-project-plugin/pull/12 ?? 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-27836) When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build.
stephenconnolly created JENKINS-27836 When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build. Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Apr/15 8:42 AM Description: This use to not be an issue as the archiving is in most case the last post-build action, but in a workflow context a manual step can be set that will hung the execution, and further steps may rely on the archived artifact. Project: Jenkins Labels: workflow Priority: Minor Reporter: stephenconnolly 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] [groovy-plugin] (JENKINS-27833) Groovy-All Bundle not deployed for BSIM Test Cases in CDB
vjuranek commented on JENKINS-27833 Groovy-All Bundle not deployed for BSIM Test Cases in CDB Hi, are you sure this is intended to be filed as an upstream issue? Besides the fact I'm not sure what BSIM and CDS stands for, the server you are referring to is not publicly available. Seems to me like some internal Ericsson 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] [cobertura-plugin] (JENKINS-27837) Cobertura plugin creates non-importable xml
Eugen Martynov created JENKINS-27837 Cobertura plugin creates non-importable xml Issue Type: Bug Assignee: stephenconnolly Attachments: config.xml Components: cobertura-plugin Created: 08/Apr/15 8:43 AM Description: I setup the cobertura coverage report in my iOS jenkins job. After I modifying slightly the SCM part and copying xml to jenkins for feature branches. Unfortunately all post build actions are lost. I've created SO question: http://stackoverflow.com/questions/29488210/jenkins-doesnt-load-publishers-section-from-config-xml And as suggested I found next error: hudson.plugins.cobertura.targets.CoverageMetric.METHOD : No enum const class hudson.plugins.cobertura.targets.CoverageMetric.METHOD Debugging information message : No enum const class hudson.plugins.cobertura.targets.CoverageMetric.METHOD cause-exception : java.lang.IllegalArgumentException cause-message : No enum const class hudson.plugins.cobertura.targets.CoverageMetric.METHOD class : hudson.plugins.cobertura.targets.CoverageMetric required-type : hudson.plugins.cobertura.targets.CoverageMetric converter-type : com.thoughtworks.xstream.converters.enums.EnumConverter path : /project/publishers/hudson.plugins.cobertura.CoberturaPublisher/healthyTarget/targets/entry/hudson.plugins.cobertura.targets.CoverageMetric line number : 3 class1 : java.util.EnumMap converter-type1 : com.thoughtworks.xstream.converters.enums.EnumMapConverter ---, MissingFieldException: No field 'int' found in class 'hudson.plugins.cobertura.targets.CoverageTarget', MissingFieldException: No field 'entry' found in class 'hudson.plugins.cobertura.CoberturaPublisher', MissingFieldException: No field 'entry' found in class 'hudson.plugins.cobertura.CoberturaPublisher', ConversionException: hudson.plugins.cobertura.targets.CoverageTarget cannot be cast to hudson.util.DescribableList : hudson.plugins.cobertura.targets.CoverageTarget cannot be cast to hudson.util.DescribableList Debugging information message : hudson.plugins.cobertura.targets.CoverageTarget cannot be cast to hudson.util.DescribableList cause-exception : java.lang.ClassCastException cause-message : hudson.plugins.cobertura.targets.CoverageTarget cannot be cast to hudson.util.DescribableList class : hudson.util.DescribableList required-type : hudson.plugins.cobertura.targets.CoverageTarget converter-type : hudson.util.DescribableList$ConverterImpl path : /project/publishers/hudson.plugins.cobertura.CoberturaPublisher/healthyTarget line number : 5 ---, MissingFieldException: No field 'unhealthyTarget' found in class 'hudson.model.FreeStyleProject', MissingFieldException: No field 'failingTarget' found in class 'hudson.model.FreeStyleProject', MissingFieldException: No field 'sourceEncoding' found in class 'hudson.model.FreeStyleProject' I'm also attaching original xml Environment: org.jenkins-ci.main:jenkins-war:1.602 org.jenkins-ci.plugins:cobertura:1.9.7 Project: Jenkins Priority: Blocker Reporter: Eugen Martynov 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
[JIRA] [core] (JENKINS-27836) When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build.
dogfood commented on JENKINS-27836 When concurrent builds are enabled, artifact retention policy may delete artifact being used by an actually running build. Integrated in jenkins_main_trunk #4074 FIXED JENKINS-27836 Noting merge of #1570 (Revision 6e7e3c8f3ae7fd048ab34a4eb3469d89679d6949) Result = SUCCESS stephen connolly : 6e7e3c8f3ae7fd048ab34a4eb3469d89679d6949 Files : changelog.html 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
dogfood commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Integrated in jenkins_main_trunk #4074 Result = SUCCESS 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] [swarm-plugin] (JENKINS-17144) Add support for private keys for authentiation
Joshua Hoblitt commented on JENKINS-17144 Add support for private keys for authentiation I've run into the situation with GithubAuthorizationStrategy from github-oauth where the CLI must use an ssh key pair to function (-username/-password do not work it's not clear to me if this is an issue with CLI or the authorization strategy). However, swarm clients can not presently use an ssh key pair. After some thrashing around, I've discovered that swarm clients will function with the API token as the password for a user. However, the user account has to be created and the API token retrieved before clients can be configured. This is both non-orthogonal with how the CLI must authenticate and sub-optimal for configuration management. 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] [periodicbackup-plugin] (JENKINS-27849) File Management Strategy that preserves build history without artifacts
Justin Georgeson
created JENKINS-27849
File Management Strategy that preserves build history without artifacts
Issue Type:
Improvement
Assignee:
Unassigned
Components:
periodicbackup-plugin
Created:
08/Apr/15 4:26 PM
Description:
The full backup strategy produces large backups which include all the archived files (like instrumented class files source code from code coverage) from the builds, but the ConfigOnly strategy loses all build history. An intermediate strategy that includes the basic build history without the large binary files would preserve
jobs//config.xml
jobs//nextBuildNumber
jobs//builds/legacyIds
jobs//builds//.xml
jobs//builds//injectedEnvVars.txt
jobs//builds//log
Or maybe a configurable set of patterns to exclude like
jobs//builds//.jar
jobs//builds//.class
jobs//builds//.java
jobs//builds//.so
jobs//builds//.{cpp,c,C,h,hxx,cs}
jobs//builds//.exe
jobs//builds//.zip
jobs//builds//.tar
jobs//builds//.tar.{gz,gzip,bzip2,bz2,Z}
Project:
Jenkins
Priority:
Minor
Reporter:
Justin Georgeson
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] [email-ext-plugin] (JENKINS-27848) Email-ext not updating emails with changes in Jenkins
Dave Shevett created JENKINS-27848 Email-ext not updating emails with changes in Jenkins Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 08/Apr/15 4:25 PM Description: We have made changes to "Default Content" in Editable Email Notification for a job. This is in a post-build action. However, changes in this block are not reflected in the email. The config.xml for the job shows the change, and we have reloaded the configuration in jenkins. Still no update. Screenshot of the changed field: https://www.evernote.com/l/AKrSQB4mNixJaoPlkAl_H6e32nDBWSAXE7A Example of the mail received in inbox: http://note.io/1HQUiot Note the mail does not include the 'Content' or "Sanitizer summary" or similar. Is this being overriden elsewhere? Help please! Environment: Jenkins 1.563 Ubuntu Precise java version 1.6.0_34 OpenJDK Runtime Environment (IcedTea6 1.13.6) (6b34-1.13.6-1ubuntu0.12.04.1) OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) email-ext: 2.37.2.2 Project: Jenkins Priority: Major Reporter: Dave Shevett 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] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
SCM/JIRA link daemon commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java http://jenkins-ci.org/commit/email-ext-plugin/27fbded960faec271591a284709dad6dde3af4c0 Log: Fix JENKINS-27448 Remove check for output != null. 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-27847) JAVA error
Alex Earl updated JENKINS-27847 JAVA error Change By: Alex Earl (08/Apr/15 3:39 PM) Assignee: AlexEarl Component/s: core Component/s: email-ext-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] [htmlpublisher-plugin] (JENKINS-24057) Jenkins HTML publisher : latest html report not publishing project level when job fails
Daniel Horak commented on JENKINS-24057 Jenkins HTML publisher : latest html report not publishing project level when job fails I would also like to be able to see html report from failed jobs. 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] [email-ext-plugin] (JENKINS-27847) JAVA error
Alex Earl commented on JENKINS-27847 JAVA error I don't see anything in the stack trace that has anything to do with email-ext. 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] [email-ext-plugin] (JENKINS-27448) Success and failure trigger work even after setting the cancel variable to true in the pre-send script
Alex Earl commented on JENKINS-27448 Success and failure trigger work even after setting the cancel variable to true in the pre-send script The issue is actually in the code I pasted before. If the last line doesn't evaluate to some value, the output variable will be set to null and the value of cancel will never be updated. This will be fixed in the next version. 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] [email-ext-plugin] (JENKINS-27848) Email-ext not updating emails with changes in Jenkins
Alex Earl commented on JENKINS-27848 Email-ext not updating emails with changes in Jenkins Sorry, I mean the email-ext triggers. In the Advanced section of the configuration. 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] [email-ext-plugin] (JENKINS-27848) Email-ext not updating emails with changes in Jenkins
Dave Shevett commented on JENKINS-27848 Email-ext not updating emails with changes in Jenkins Only on 'Success' and... AHA! http://note.io/1alGWFA So THATS where I should be modifying the output, yes? That's confusing... I can use the same variable substitution in that section, correct? 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] [email-ext-plugin] (JENKINS-27848) Email-ext not updating emails with changes in Jenkins
Alex Earl resolved JENKINS-27848 as Not A Defect Email-ext not updating emails with changes in Jenkins Change By: Alex Earl (08/Apr/15 5:16 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] [email-ext-plugin] (JENKINS-27848) Email-ext not updating emails with changes in Jenkins
Alex Earl commented on JENKINS-27848 Email-ext not updating emails with changes in Jenkins Yes, that is where you need to modify it. If you just want to use the content from the higher level, you can use $PROJECT_DEFAULT_CONTENT in the trigger's content area. 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-26406) Build history text field wrap fails when containing markup
Daryl Spartz commented on JENKINS-26406 Build history text field wrap fails when containing markup The patch fixed a problem we discovered with html hyperlink in build description not being clickable. Please add to next LTS 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] [mercurial-plugin] (JENKINS-27827) Mercurial + Multiple SCMs changelog no longer displayed
Jesse Glick updated JENKINS-27827 Mercurial + Multiple SCMs changelog no longer displayed Probably some incompatibility w.r.t. the Multiple SCMs plugin, which I do not test with and which is prone to issues since this use case is not well supported by Jenkins core. Change By: Jesse Glick (08/Apr/15 12:37 PM) Summary: mercurialchangesnot Mercurial+MultipleSCMschangelognolonger displayed anymoreintoJenkinschangespage 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] [mercurial-plugin] (JENKINS-27827) mercurial changes not displayed anymore into Jenkins changes page
Jesse Glick updated JENKINS-27827 mercurial changes not displayed anymore into Jenkins changes page Probably some incompatibility w.r.t. the Multiple SCMs plugin, which I do not test with and which is prone to issues since this use case is not well supported by Jenkins core. Change By: Jesse Glick (08/Apr/15 12:36 PM) Component/s: multiple-scms-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] [subversion-plugin] (JENKINS-27846) When tagging a Build Policiy Violation Errors fom SVN Server are not visible
Christopher Orr moved JENKINS-27846 When tagging a Build Policiy Violation Errors fom SVN Server are not visible Change By: Christopher Orr (08/Apr/15 1:14 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 259 27846 Workflow: jira JNJira Component/s: subversion-plugin Component/s: 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-27664) Job hanging, killing not possible
Dave Rigby commented on JENKINS-27664 Job hanging, killing not possible I'm seeing a very similar stack trace: "Executor #0 for ubuntu12.04-02 : executing memcached-gerrit-master.NEW » ubuntu12.04 #2" Id=911 Group=main RUNNABLE at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3383) at java.util.regex.Pattern$Curly.match0(Pattern.java:3799) at java.util.regex.Pattern$Curly.match(Pattern.java:3761) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4244) at java.util.regex.Pattern$Curly.match0(Pattern.java:3799) at java.util.regex.Pattern$Curly.match(Pattern.java:3761) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4185) at java.util.regex.Pattern$Branch.match(Pattern.java:4131) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4185) at java.util.regex.Pattern$Branch.match(Pattern.java:4129) at java.util.regex.Pattern$Curly.match0(Pattern.java:3799) at java.util.regex.Pattern$Curly.match(Pattern.java:3761) at java.util.regex.Pattern$Branch.match(Pattern.java:4129) at java.util.regex.Pattern$Begin.match(Pattern.java:3137) at java.util.regex.Matcher.search(Matcher.java:1116) at java.util.regex.Matcher.find(Matcher.java:552) at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86) at hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:94) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:280) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:259) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:399) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:321) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:319) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1701) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Looks like a possible issue with the Warnings parser. We are running: Jenkins v1.553 Warnings Plugin v4.4.2 Static Code Analysis Plug-ins v1.6.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] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Derk-Jan Hartman created JENKINS-27845 Support auto install on Mac OS X Issue Type: Improvement Assignee: Unassigned Components: nodejs-plugin Created: 08/Apr/15 12:55 PM Description: The documentation of the plugin notes that auto installation for mac and windows is currently not support. I would love to hear what was blocking this to make it work. Then I might even be motivated to look into fixing it Project: Jenkins Priority: Minor Reporter: Derk-Jan Hartman 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] [email-ext-plugin] (JENKINS-27847) JAVA error
NARAYAN PRADHAN created JENKINS-27847 JAVA error Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 08/Apr/15 1:37 PM Description: we are getting below error at the end of the job === FATAL: Remote call on Rhel5.7-2014-supbl605 failed java.io.IOException: Remote call on Rhel5.7-2014-supbl605 failed at hudson.remoting.Channel.call(Channel.java:760) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:941) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:556) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.ClassFormatError: Failed to load javax.servlet.ServletException at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:325) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at hudson.util.ProcessTree.getKillers(ProcessTree.java:151) at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:212) at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:557) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:564) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:488) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:953) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:944) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) at ..remote call to Rhel5.7-2014-supbl605(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) ... 6 more Caused by: java.lang.UnsupportedClassVersionError: javax/servlet/ServletException : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:323) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at hudson.util.ProcessTree.getKillers(ProcessTree.java:151) at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:212) at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:557) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:564) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:488) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:953) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:944) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: Back to Project link not navigating
Jesse Glick updated JENKINS-27571 Workflow Job: Back to Project link not navigating First of all, please update the Workflow plugins; 1.5 should be offered to you in the update center. What is the URL of the page you see this link on, and what is the link target (according to Copy Link or whatever from your browser), and what is the actual HTML text of the link (a href=""Back to Project/a)? Change By: Jesse Glick (08/Apr/15 12:33 PM) Labels: user-experience workflow 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] [promoted-builds-plugin] (JENKINS-26819) Allow a previous build to be promoted while new build is in progress
Kari Sivonen commented on JENKINS-26819 Allow a previous build to be promoted while new build is in progress And same issue when wanted to get promotion before build is end. E.g we have a job which trigger build, static analyses and some tests. I like to get promotion after static analysis and second promotion after build. Promotion starts but there is failure mark in promotion and log is almost empty until build ends and then promotion happens. So promotio is started, but for some reason it will never get done before actual build job is finished. And same if next build is already started, it wait until it is end. 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] [workflow-plugin] (JENKINS-25550) Hard kill
Jesse Glick commented on JENKINS-25550 Hard kill Well I never tested the workaround on Windows; then you run into file locking issues. Not clear from the stack trace which file in the build directory is in use (the File Leak Detector plugin would be able to say). Extreme workaround would be to delete the named directory while Jenkins is not running. 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-27825) Can Jenkins invoke Cigital SecureAssist reports?
Jeremy Rojas commented on JENKINS-27825 Can Jenkins invoke Cigital SecureAssist reports? Hi Daniel, thanks for your reply. Would you be able to point me to another site/contact/group of people who might know more about my question? Thanks. 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-27454) Create component for aws-lambda
Daniel Beck assigned JENKINS-27454 to Daniel Beck Create component for aws-lambda Change By: Daniel Beck (08/Apr/15 12:45 PM) Assignee: DanielBeck 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] [subversion-plugin] (JENKINS-27846) When tagging a Build Policiy Violation Errors fom SVN Server are not visible
Christopher Orr commented on JENKINS-27846 When tagging a Build Policiy Violation Errors fom SVN Server are not visible Moved this issue as it was misfiled in the INFRA project. Presumably each instance of "jasper" in the description should be "Jenkins"; otherwise, I don't understand what this issue is about. 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] [pmd-plugin] (JENKINS-27828) Module Detection
Ulli Hafner resolved JENKINS-27828 as Not A Defect Module Detection Yes. But you need a pom.xml or build.xml file. Please use the mailing lists for such questions. Change By: Ulli Hafner (08/Apr/15 1:33 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] [saml-plugin] (JENKINS-27423) User ID is non-sensical using saml-plugin
Christopher Orr updated JENKINS-27423 User ID is non-sensical using saml-plugin Change By: Christopher Orr (08/Apr/15 2:05 PM) Component/s: saml-plugin Component/s: other 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] [subversion-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman commented on JENKINS-27620 SCM polling broken for servers with variable in path My issue seems duplicate with JENKINS-22542 Downgrading to 2.4.5 indeed made polling work again. 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-failure-analyzer-plugin] (JENKINS-26969) I like it is possible to select that BFA set failed build status as ABORTED
Kari Sivonen closed JENKINS-26969 as Not A Defect I like it is possible to select that BFA set failed build status as ABORTED I closed this as it was too tailored for our usage. Change By: Kari Sivonen (08/Apr/15 6:23 PM) 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] [build-failure-analyzer-plugin] (JENKINS-25751) Add to build log indication if a known cause was found
Kari Sivonen commented on JENKINS-25751 Add to build log indication if a known cause was found Now I think pull request is ready. All test is passed. If you not see anything wrong it, please merge to trunk. Or how this should continue? 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] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
Katherine Elliott commented on JENKINS-23152 builds getting lost due to GerritTrigger I can't tell what action has been taken on this defect recently. I installed http://repo.jenkins-ci.org/releases/com/sonyericsson/hudson/plugins/gerrit/gerrit-trigger/2.13.0-beta-2/gerrit-trigger-2.13.0-beta-2.hpi on my Jenkins server and, although it did seem to fix the "missing builds" issue, now I'm only getting one of multiple jobs reporting results back to Gerrit! When I submit a patch set to our Gerrit server, I only get one email but that email shows that two jobs were triggered. When I go to the review in Gerrit, it only shows one of the two jobs being triggered. Has anyone else seen 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] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
Katherine Elliott edited a comment on JENKINS-23152 builds getting lost due to GerritTrigger I can't tell what action has been taken on this defect recently. I installed http://repo.jenkins-ci.org/releases/com/sonyericsson/hudson/plugins/gerrit/gerrit-trigger/2.13.0-beta-2/gerrit-trigger-2.13.0-beta-2.hpi on my Jenkins server and, although it did seem to fix the "missing builds" issue, now I'm only getting one of multiple jobs reporting results back to Gerrit! When I submit a patch set to our Gerrit server, I only get one email but that email shows that two jobs were triggered. When I go to the review in Gerrit, it only shows one of the two jobs being triggered. This is what I see in Gerrit: jenkins 12:32 PM ↩ Patch Set 1: Build Started http://jenkins-instance:8080/job/test-2/37/ (2/2) I should be seeing: jenkins 12:32 PM ↩ Patch Set 1: Build Started http://jenkins-instance:8080/job/test-1/37/ (1/2) Build Started http://jenkins-instance:8080/job/test-2/37/ (2/2) Has anyone else seen 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] [core] (JENKINS-27852) order of post build actions not being respected
Arpit Gupta commented on JENKINS-27852 order of post build actions not being respected I had sent a mail to the user list but did not get a definitive answer if the assumption that the order in which the post build actions are specified are the order they will be executed in so i decided to log this bug. 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-27852) order of post build actions not being respected
Arpit Gupta created JENKINS-27852 order of post build actions not being respected Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Apr/15 6:40 PM Description: We have multiple post build actions and one of them was to delete the workspace. What i noticed is that even if that action is the last one (assuming the order they appear in is the order they are executed) it was executed earlier. Noticed this because other post build actions wanted to refer to scripts/files in the workspace. Project: Jenkins Priority: Critical Reporter: Arpit Gupta 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-27852) order of post build actions not being respected
Arpit Gupta edited a comment on JENKINS-27852 order of post build actions not being respected Also do not recall exactly what version of jenkins it started in. We are currently on 1.607 I had sent a mail to the user list but did not get a definitive answer if the assumption that the order in which the post build actions are specified are the order they will be executed in so i decided to log this bug. 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] [description-setter-plugin] (JENKINS-27824) Build Descriptions containing br are no longer rendered correctly on project page (but are renedered correctly on build page)
M Chon edited a comment on JENKINS-27824 Build Descriptions containing br are no longer rendered correctly on project page (but are renedered correctly on build page) In Global Security, we are using 'Safe HTML'. Prior to the 1.596.1 Jenkins upgrade, all of our servers were set to use 'Raw HTML'- which no longer seems to be an option in the dropdown list. On a test project, I manually edited the description to change it from a single line to this: d9489496brline2brline3brline4 Then I saved the project, and navigated back to the main project page to look at the list of builds. Interestingly, I am almost 100% sure I briefly saw it being rendered in multiple lines, but then it redrew (??) itself and now looks like the attached screen shot. (multi-line-rendered-as-single-line-Safe-HTML) I will try using 'Escaped HTML' on one of our test servers to see what it does. 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.
