[JIRA] [scm-sync-configuration-plugin] (JENKINS-26652) SCM Sync fails after deleting a project
thedug assigned JENKINS-26652 to Unassigned SCM Sync fails after deleting a project Change By: thedug (21/Feb/15 7:57 AM) Assignee: thedug 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-26652) SCM Sync fails after deleting a project
thedug assigned JENKINS-26652 to thedug SCM Sync fails after deleting a project Change By: thedug (21/Feb/15 7:56 AM) Assignee: Frédéric Camblor thedug 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 I decrease quantity of executors to one. Thus allow only execute one build job art time. It works much more reliable, but, of course, very slow. We have hundreds build job, to rebuild entire tree with only one executor, it will take about a day! The SQL exception related to the Table/View, still appeared like the following A SQL Exception was caught! Table/View 'SCM_8804D8BF_B059_4FCE_AD3C_93A872EEC42A' does not exist. 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] [copy-to-slave-plugin] (JENKINS-25346) "Copy files back to master node" doesn't copy to workspace
Vivekanand SV commented on JENKINS-25346 "Copy files back to master node" doesn't copy to workspace @Daniel, getWorkspaceFor() accepts only an implementation of TopLevelItem, so this will work in case of a free style project, what about other cases ? I tried Jenkins javadoc for some time but I couldn't get a clue. Sorry for posting these questions, I don't have much knowledge about Jenkins code so looking for all 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] [email-ext-plugin] (JENKINS-23126) email-ext should be able to send emails in both HTML and text
SCM/JIRA link daemon commented on JENKINS-23126 email-ext should be able to send emails in both HTML and text Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/plugins/CssInliner.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.properties src/main/resources/hudson/plugins/emailext/plugins/EmailTrigger/config.groovy src/main/resources/hudson/plugins/emailext/plugins/EmailTrigger/config.properties src/test/java/hudson/plugins/emailext/EmailTypeTest.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptorTest.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java src/test/java/hudson/plugins/emailext/plugins/CssInlinerTest.java src/test/resources/plugins/config-file-provider/config-file-provider.hpi http://jenkins-ci.org/commit/email-ext-plugin/7ab3d5966c7f4454d44dd0f1c8c1037262f20563 Log: Fix JENKINS-23126 Added option to send in both HTML and plain text. The plain text version is a stripped version of the HTML using the Jericho library. Compare: https://github.com/jenkinsci/email-ext-plugin/compare/8a47a78f5ed9...7ab3d5966c7f 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-26286) Can not use token (like WARNINGS_NEW) in pre-send script email
SCM/JIRA link daemon commented on JENKINS-26286 Can not use token (like WARNINGS_NEW) in pre-send script email Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java http://jenkins-ci.org/commit/email-ext-plugin/72fcd04ef301a8e45df268945ce48fa146aa56ca Log: Fix JENKINS-26286 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 I just decrease quantity of executors to one. Thus allow only execute one build job art time. It works much more reliable, but, of course, very slow. We have hundreds build job, to rebuild entire tree with only one executor, it will take about a day! 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 It looks like there are different errors here (see attached error log file) Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. The bad thing is that problem intermittent, sometimes it works, sometimes does not This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman updated JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 Change By: Grigoriy Milman (21/Feb/15 5:19 AM) Priority: Major Blocker 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 It looks like there are different errors here (see attached error log file) Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman updated JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 It looks like there are different errors here Syntax error: Encountered "WHERE" ... java.lang.NullPointerException java.sql.SQLSyntaxErrorException: Table/View 'SCM_42320538_D24A_465E_A61D_4D1D6E1E3E8C' does not exist. Change By: Grigoriy Milman (21/Feb/15 5:19 AM) Attachment: jenkins.err.log 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-23126) email-ext should be able to send emails in both HTML and text
Alex Earl resolved JENKINS-23126 as Fixed email-ext should be able to send emails in both HTML and text Added option to send both HTML and plain text. The plain text is a stripped version of the HTML using Jericho. Change By: Alex Earl (21/Feb/15 5:15 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] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
sogabe commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value What's the status now? 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman edited a comment on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 10 minutes later, this build job was successfully done when was started and running stand alone! It is very strange. By the way (just observation), it looks like "Preparing to execute si projectinfo for..." only running for one build job a time, and if in parallel another build job already doing this operation, everything stack 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 10 minutes later, this build job was successfully done when was started and running stand alone! It is very strange. 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] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 I have tried again to build the same build job alone: Time Elapsed 00:00:00.22 Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@e4f765 Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Retrying after 10 seconds Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/944/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Table/View 'SCM_974E0F36_678A_4802_AE9C_0FA142C071CA' does not exist. Archiving artifacts Publishing Javadoc Recording fingerprints Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Gennady Feldman commented on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Feb 19, 2015 8:49:48 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving http://jenkins/ghprbhook/ java.lang.reflect.InvocationTargetException 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.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$2.dispatch(MetaClass.java:165) 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.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 hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) 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.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 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:135) 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.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.
[JIRA] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Gennady Feldman commented on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Feb 19, 2015 8:35:25 PM hudson.model.listeners.RunListener report WARNING: RunListener failed java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbRepository.createCommitStatus(GhprbRepository.java:140) at org.jenkinsci.plugins.ghprb.GhprbRepository.createCommitStatus(GhprbRepository.java:122) at org.jenkinsci.plugins.ghprb.GhprbBuilds.onStarted(GhprbBuilds.java:81) at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onStarted(GhprbBuildListener.java:19) at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onStarted(GhprbBuildListener.java:12) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:213) at hudson.model.Run.execute(Run.java:1714) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Gennady Feldman commented on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Feb 19, 2015 8:35:20 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving http://jenkins/ghprbhook/ java.lang.reflect.InvocationTargetException 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.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$2.dispatch(MetaClass.java:165) 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.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 hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) 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.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 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:135) 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:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
[JIRA] [integrity-plugin] (JENKINS-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman created JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 21/Feb/15 4:37 AM Description: PTC plugin 1.31 - generally works but suddenly we have observed a strange bug: Multiple build jobs started about simultaneously (not sure is it important or not) Time Elapsed 00:00:00.95 Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@e4f765 Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/943/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP.Direct.Components.Sequencer/943/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj An API Exception was caught! Authentication failed for TE_build_process on mks1.biotronik.de:7001 si projectinfo --user=TE_build_process --port=7001 --hostname=mks1.biotronik.de --project=/repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj – returned exit code 128 Retrying after 10 seconds Change Log: http://-.com:8080/job/NGMP.Direct.Components.Sequencer/943/changes Build Log: http://-.com:8080/job/NGMP.Direct.Components.Sequencer/943/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Components/Sequencer/Sequencer.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=Components/Components.pj#s=Sequencer/Sequencer.pj A SQL Exception was caught! Table/View 'SCM_18987648_BDEE_4233_9A45_E1E0A4B3DE60' does not exist. Retrying after 10 seconds Build was aborted Environment: Windows, Jenkins 1.598 PTC plugin 1.31 Project: Jenkins Priority: Major Reporter: Grigoriy Milman 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-monitor-plugin] (JENKINS-27060) Show last build description
Tony Lampada updated JENKINS-27060 Show last build description Change By: Tony Lampada (21/Feb/15 4:32 AM) Component/s: build-monitor-plugin Component/s: monitoring-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] [monitoring-plugin] (JENKINS-27060) Show last build description
Tony Lampada created JENKINS-27060 Show last build description Issue Type: New Feature Assignee: Unassigned Components: monitoring-plugin Created: 21/Feb/15 4:30 AM Description: In our build, we use the description setter plugin to add details about each builds for quick visualization. This is a typical build description for one broken build: dev[212ff3f5..591ed136] by tonylampada / DEU PAU no Flake8 (status: 1) It is nice that the monitor shows possible culprits. For our use case though, it would be even more useful to display the last build description. How do you feel about supporting this use case? Project: Jenkins Priority: Minor Reporter: Tony Lampada 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-27046) Restarted the master and all slaves went offline
Aditya Inapurapu edited a comment on JENKINS-27046 Restarted the master and all slaves went offline Daniel, Yes, this was caused by a limitation in the environment. At the same time, could Jenkins possibly add a more appropriate log entry like 'Cannot start more slaves. Memory allocation of user is too low.'? An error like 'java.io.EOFException', 'Trying to unexport an object that's already unexported', 'ERROR: Connection terminated' did not lead us in the right direction. 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-27046) Restarted the master and all slaves went offline
Aditya Inapurapu commented on JENKINS-27046 Restarted the master and all slaves went offline Daniel, Yes, this was caused by a limitation in the environment. At the same time, could Jenkins possibly add a more appropriate log entry like 'Cannot start more slaves. Memory allocation of user is too low.'? An error like 'java.io.EOFException', 'Trying to unexport an object that's already unexported', 'ERROR: Connection terminated' did not lead us in the right direction. If possible, please change this from a defect to an enhancement request. 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] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Mark Waite commented on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Can you provide the stack trace so that it can be used to make guesses about what change in the git plugin caused the exception? 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] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Gennady Feldman commented on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin What happened was that any builds that were supposed to have been triggered from GitHub PRs through the ghprb-plugin would fail to start. GitHub would show that the webhook was sent but the response came back as 500 (Internal Server Error) Looks like when GitHub sends the payload via the ghprb-plugin webhook. ghprb-plugin starts to parse the payload and hits a "Null Pointer Exception" and fails to trigger a build to start. So the Jenkins builds are never executed. Rolling back the Git Plugin to 2.3.4 makes things work again. I am running latest version(s) of Jenkins, Git Client, ghprb-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] [ircbot-plugin] (JENKINS-27059) IRC plug spawns threads & does not release them
Ian Itow created JENKINS-27059 IRC plug spawns threads & does not release them Issue Type: Bug Assignee: kutzi Components: ircbot-plugin Created: 21/Feb/15 3:16 AM Description: Steps to re-create the issue. 1) setup an irc server. 2) setup 2 jenkins instances 3) Install the ircbot 2.25 latest on each server 4) in global configurations of each server point both servers to the same channel #waldo. 5) wait approx 5 days 6) Monitor the server with the error log: Caused by: org.pircbotx.exception.NickAlreadyInUseException: Nickname is already in use. Eventually the botXX-outputs threads will reach 1024 threads and lock up jenkins server however, the error will just be: java.lang.OutOfMemoryError: unable to create new native thread The backtrace is useless because it will be cause by whatever thread you started. Use Jconsole and enable jmx on jenkins.war and you can see the botXX-output threads stackup and slowly strangle Jenkins into a grave. Environment: * CentOS release 6.5 (Final) * Jenkins ver. 1.588 * plugins list: Plugin:github Plugin:cloudbees-enterprise-plugins Plugin:cvs Plugin:git-server Plugin:windows-slaves Plugin:ant Plugin:github-api Plugin:build-pipeline-plugin Plugin:pam-auth Plugin:ssh-slaves Plugin:antisamy-markup-formatter Plugin:javadoc Plugin:subversion Plugin:mailer Plugin:ownership Plugin:groovy-postbuild Plugin:credentials Plugin:postbuild-task Plugin:ldap Plugin:git Plugin:external-monitor-job Plugin:junit Plugin:matrix-auth Plugin:git-client Plugin:ssh-credentials Plugin:matrix-project Plugin:cloudbees-folder Plugin:maven-plugin Plugin:next-build-number Plugin:translation Plugin:cloudbees-credentials Plugin:mercurial Plugin:openid Plugin:active-directory Plugin:testopia Plugin:scm-api Plugin:scriptler Plugin:suppress-stack-trace Plugin:jobrequeue Plugin:conditional-buildstep Plugin:build-name-setter Plugin:promoted-builds Plugin:shelve-project-plugin Plugin:ansicolor Plugin:ssh-agent Plugin:copy-project-link Plugin:async-http-client Plugin:copyartifact Plugin:rebuild Plugin:greenballs Plugin:script-security Plugin:preSCMbuildstep Plugin:job-import-plugin Plugin:metrics Plugin:template-project Plugin:build-view-column Plugin:instant-messaging Plugin:gitlab-merge-request-jenkins Plugin:durable-task Plugin:jobConfigHistory Plugin:parameterized-trigger Plugin:ssh Plugin:thinBackup Plugin:config-file-provider Plugin:support-core Plugin:build-token-root Plugin:mapdb-api Plugin:groovy Plugin:view-job-filters Plugin:monitoring Plugin:description-setter Plugin:role-strategy Plugin:job-dsl Plugin:managed-scripts Plugin:envinject Plugin:swarm Plugin:postbuildscript Plugin:extended-choice-parameter Plugin:jquery Plugin:openid4java Plugin:build-monitor-plugin Plugin:run-condition Plugin:node-iterator-api Plugin:nodelabelparameter Plugin:token-macro Plugin:gravatar Plugin:bugzilla Plugin:publish-over-ssh Plugin:build-timeout Plugin:ircbot Plugin:PrioritySorter Plugin:build-user-vars-plugin Plugin:dashboard-view Plugin:dynamic_extended_choice_parameter Project: Jenkins Labels: plugin jenkins deadlock threads kill Priority: Critical Reporter: Ian Itow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA adm
[JIRA] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Mark Waite updated JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Change By: Mark Waite (21/Feb/15 3:12 AM) Component/s: ghprb-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] [ghprb-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Mark Waite edited a comment on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Please provide more details of the conditions which cause the failure so that it can be duplicated. Please provide a stack trace, if one is available in the log. Please provide any hints of the actions taken which cause the null pointer exceptions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Mark Waite commented on JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Please provide more details of the conditions which cause the failure so that it can be duplicated. 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-27058) hudson.model.Slave#remoteFS must be absolute, but this is not enforced
recampbell edited a comment on JENKINS-27058 hudson.model.Slave#remoteFS must be absolute, but this is not enforced I think that the Slave constructor should throw a FormException if the remoteFS is not absolute since there is no way to guess at what the absolute path should be. 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-27058) hudson.model.Slave#remoteFS must be absolute, but this is not enforced
recampbell commented on JENKINS-27058 hudson.model.Slave#remoteFS must be absolute, but this is not enforced I think that the constructor should throw a FormException if the remoteFS is not absolute since there is no way to guess at what the absolute path should be. 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] [xcode-plugin] (JENKINS-15118) Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project
Alvin Wong updated JENKINS-15118 Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project Running into similar issue I think. Project builds fine but the technical version is not changed in the info.plist. Change By: Alvin Wong (21/Feb/15 12:12 AM) Attachment: log.txt 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-27058) hudson.model.Slave#remoteFS must be absolute, but this is not enforced
Jesse Glick updated JENKINS-27058 hudson.model.Slave#remoteFS must be absolute, but this is not enforced Change By: Jesse Glick (20/Feb/15 11:53 PM) Labels: robustness slave 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-restrictions-plugin] (JENKINS-26874) Restricting build execution cause does not work
Jesse Glick updated JENKINS-26874 Restricting build execution cause does not work Change By: Jesse Glick (20/Feb/15 11:50 PM) Labels: workflow Assignee: Jesse Glick Component/s: job-restrictions-plugin 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] [workflow-plugin] (JENKINS-26692) build step should allow specification of custom delay
Jesse Glick updated JENKINS-26692 build step should allow specification of custom delay Change By: Jesse Glick (20/Feb/15 11:51 PM) Summary: RFE: workflow-plugin: specify job delay when running a build job step should allow specification of custom delay 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-26298) Console output does not scroll anymore
Ramakrishna P commented on JENKINS-26298 Console output does not scroll anymore Hi Daniel, Thanks, for your quick reply. No, i am not using any special version ( Bitnami Jenkins ) / professional version of Jenkins. I am using the regular / OSS version of Jenkins in my test instance. Probably i may not be clear regarding the issue details. The issue is one I trigger my job and go n see the console output it is not showing the latest console output when the build is running. All it shows in " Spinning Icon " and it didn't get SCROLL THE LATEST LOG AT ALL. Once I refresh the page then it is loading the latest LOG. Thanks, Ramakrishna 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-26919) Workflow Plugin : 1 master 6 local slaves : setting env var using 'env' per slave fails
Jesse Glick resolved JENKINS-26919 as Not A Defect Workflow Plugin : 1 master 6 local slaves : setting env var using 'env' per slave fails The very last env setting in the last slave execution OVERRIDES the values in the other slaves. Is this behaviour expected? Yes. Tutorial Change By: Jesse Glick (20/Feb/15 11:48 PM) Status: Open Resolved Resolution: Not A Defect 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-26298) Console output does not scroll anymore
Ramakrishna P updated JENKINS-26298 Console output does not scroll anymore Please, find the attached JPG file for the version of Jenkins I am using. Change By: Ramakrishna P (20/Feb/15 11:47 PM) Attachment: Jenkins_Version.jpg 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-26987) Hiding certain steps from the "Running Steps" tree
Jesse Glick resolved JENKINS-26987 as Won't Fix Hiding certain steps from the "Running Steps" tree Running Steps is itself intended to be a debugging view, and so should show all steps. For routine examination of builds, see the text console (or the stage view if you have Jenkins Enterprise). Change By: Jesse Glick (20/Feb/15 11:46 PM) Status: Open Resolved Resolution: Won't Fix 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-27039) Option for input step to cancel older executions
Jesse Glick updated JENKINS-27039 Option for input step to cancel older executions So you are asking for an option to input to kill older step executions with the same ID. I suppose this could be useful. Independent of the stage step in that case. Change By: Jesse Glick (20/Feb/15 11:44 PM) Summary: User Option for input in a stage step to cancel older executions Issue Type: Improvement New Feature 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-26640) svn: E175002: handshake alert: unrecognized_name
Daniel Beck commented on JENKINS-26640 svn: E175002: handshake alert: unrecognized_name First google hit for the error message points to http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0 Have you tried that? 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-27046) Restarted the master and all slaves went offline
Daniel Beck commented on JENKINS-27046 Restarted the master and all slaves went offline The default physical memory allocated in Redhat to a user profile is 1gb which is quite low for our needs. Disk space or RAM? This looks more like a limitation of your specific environment than any sensible vendor default. 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] [remoting] (JENKINS-2110) # of executors field help states you can enter 0, but you cannot
Daniel Beck resolved JENKINS-2110 as Fixed # of executors field help states you can enter 0, but you cannot Resolving again, because the help states: Slaves may not have zero executors, but may be temporarily disabled using the button on the slave's status page. So clearly it's not like the help says it's allowed. The form validation will also complain about values lower than 1. Jenkins will allow you to submit forms that have errors and result in exceptions being thrown, which admittedly can be weird, but a completely different issue. Change By: Daniel Beck (20/Feb/15 11:21 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pegdown-formatter-plugin] (JENKINS-27049) PegDown formatter causes deprecation message in jenkins log
Daniel Beck resolved JENKINS-27049 as Not A Defect PegDown formatter causes deprecation message in jenkins log Not an issue in PegDown – it appears in core, and core-bundled plugins as well – it's just that Stapler sucks so much right now. https://github.com/stapler/stapler/pull/39#issuecomment-64078010 Change By: Daniel Beck (20/Feb/15 11:16 PM) Status: Open Resolved Resolution: Not A Defect 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] [bitbucket-plugin] (JENKINS-27047) Plugin does not work
Daniel Beck resolved JENKINS-27047 as Not A Defect Plugin does not work This is an issue tracker, not a support site. Change By: Daniel Beck (20/Feb/15 11:13 PM) Status: Open Resolved Resolution: Not A Defect 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] [analysis-core-plugin] (JENKINS-25905) Parameterized view on Warnings trend
Ulli Hafner commented on JENKINS-25905 Parameterized view on Warnings trend Do you mean at the top level? At the configuration level the graphs are already plotted by configuration? Should there be n graphs or should the graph have a input field to choose the configuration to visualize? 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] [analysis-core-plugin] (JENKINS-25905) Parameterized view on Warnings trend
Ulli Hafner edited a comment on JENKINS-25905 Parameterized view on Warnings trend Do you mean at the top level? At the configuration level the graphs are already plotted by configuration? Should there be n graphs or should the graph have an input field to choose the configuration to visualize? 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] [analysis-core-plugin] (JENKINS-25906) Incremental builds are not represented in Warnings plugin
Ulli Hafner resolved JENKINS-25906 as Won't Fix Incremental builds are not represented in Warnings plugin I don't think that this is easy to implement. More over, one import pattern of CI is to do always full builds and no incremental builds. Change By: Ulli Hafner (20/Feb/15 11:06 PM) Status: Open Resolved Resolution: Won't Fix 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] [analysis-core-plugin] (JENKINS-26235) Tab customizations
Ulli Hafner commented on JENKINS-26235 Tab customizations Good to see. Adding new tabs is not that easy... This needs to be adapted in the main.jelly and in the detail factories. 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] [warnings-plugin] (JENKINS-26682) Can't parse jslint-formatted XML file
Ulli Hafner commented on JENKINS-26682 Can't parse jslint-formatted XML file As far as I understand the architecture the file is parsed on the master. I have no clue what is broken in your setup. 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-26298) Console output does not scroll anymore
Daniel Beck commented on JENKINS-26298 Console output does not scroll anymore After the upgrade we are started seeing this " Console Output Refresh " was not happening and it is troubling a lot. This issue is about the scrolling not working. The console still gets updated otherwise. If the console does not get updated, make sure you're not using the Bitnami Jenkins distribution (see JENKINS-25026), it's broken. 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-26640) svn: E175002: handshake alert: unrecognized_name
Curt Clayton reopened JENKINS-26640 svn: E175002: handshake alert: unrecognized_name I appreciate that there is a workaround, but the workaround is not feasible considering the current Oracle support plan for Java 6 (EOS 2013) and 7 (EOS April, 2015). Change By: Curt Clayton (20/Feb/15 10:38 PM) Resolution: Fixed Status: Resolved Reopened 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-26298) Console output does not scroll anymore
Ramakrishna P commented on JENKINS-26298 Console output does not scroll anymore Hi Guys, Sorry, for posting about this issue very late. Today we have upgraded our Jenkins instance from 1.558 to 1.599 and we started seeing lot of changes in the UI and configurations. After the upgrade we are started seeing this " Console Output Refresh " was not happening and it is troubling a lot. After searching for the fix we got to know that it has been already addressed in the Ver. 1.598 itself. But still we are seeing this issue in the latest version 1.599. Can someone help us regarding this issue and let us know do we need to make any change in the configuration to fix the issue ? Thanks, Ramakrishna 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-26912) 'build' workflow command ignores parameters, triggering default-only builds
Jesse Glick
resolved JENKINS-26912 as Not A Defect
'build' workflow command ignores parameters, triggering default-only builds
JENKINS-26093 covers the task of making the snippet generator work properly for this step, as well as core changes to simplify the syntax. Currently you need to use, for example,
build job: 'My Test Job', parameters: [new hudson.model.StringParameterValue('version', 'master')]
Change By:
Jesse Glick
(20/Feb/15 10:12 PM)
Status:
Open
Resolved
Resolution:
Not A Defect
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-27052) It is possible to have multiple instances of a workflow in the same stage, even with `concurrency:1`
Jesse Glick started work on JENKINS-27052 It is possible to have multiple instances of a workflow in the same stage, even with `concurrency:1` Change By: Jesse Glick (20/Feb/15 9:51 PM) Status: Open In Progress 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] [sauce-ondemand-plugin] (JENKINS-26662) Sauce connect options does not allow the use of more than one environment variable at a time
Ross Rowe resolved JENKINS-26662 as Fixed Sauce connect options does not allow the use of more than one environment variable at a time A fix for this issue has been included in v1.116 Change By: Ross Rowe (20/Feb/15 8:37 PM) Status: In Progress 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] [core] (JENKINS-27046) Restarted the master and all slaves went offline
Aditya Inapurapu commented on JENKINS-27046 Restarted the master and all slaves went offline The default physical memory allocated in Redhat to a user profile is 1gb which is quite low for our needs. We increased this to 3gb and the issue did not reoccur. We changed the priority of this defect to minor. We will leave the ticket open and so that some enhancements to Jenkins can be made using this information. Perhaps Jenkins could check on the physical memory allocation on start up or restart. 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-27046) Restarted the master and all slaves went offline
Aditya Inapurapu updated JENKINS-27046 Restarted the master and all slaves went offline Change By: Aditya Inapurapu (20/Feb/15 7:49 PM) Priority: Major Minor 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-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException
Thomas Jones-Low commented on JENKINS-18687 Intermittent failure whilst recording test results caused by java.util.MissingResourceException New datapoint. In our Jenkins (v 1.598) configuration we have two Maven installations. First is Maven 3.0.5, the second is Maven 3.2.2. Both configured to install from Apache. I have one maven Job which does a "mvn -U clean install". When configured for the 3.0.5 version of maven, the JUnit gathering test results fails with the MissingResourceException. If I change the job to use Maven 3.2.2, the JUnit gathering results succeeds and the Job passes. 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-27058) hudson.model.Slave#remoteFS must be absolute, but this is not enforced
recampbell updated JENKINS-27058 hudson.model.Slave#remoteFS must be absolute, but this is not enforced Change By: recampbell (20/Feb/15 6:47 PM) Description: According to the javadoc, hudson.model.Slave#remoteFS is intended to be absolute, but there is nothing which enforces this as an invariant. As a result of this bug, other plugins which rely upon this contract for remoteFS will break in mysterious ways if a slave is created which doesn't obey this contract.It may be that the default Slave implementations correctly absolutize the root path, but there's at least one implementation which doesn't. So it needs enforcing. 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-27058) hudson.model.Slave#remoteFS must be absolute, but this is not enforced
recampbell created JENKINS-27058 hudson.model.Slave#remoteFS must be absolute, but this is not enforced Issue Type: Bug Assignee: Unassigned Components: core Created: 20/Feb/15 6:45 PM Description: According to the javadoc, hudson.model.Slave#remoteFS is intended to be absolute, but there is nothing which enforces this as an invariant. Project: Jenkins Priority: Minor Reporter: recampbell 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] [remoting] (JENKINS-2110) # of executors field help states you can enter 0, but you cannot
Phil Miller
commented on JENKINS-2110
# of executors field help states you can enter 0, but you cannot
Specifically, here's the stack trace I got when I entered '0' in the "# of executors" field for a node and clicked 'Save':
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.slaves.DumbSlave from {"name":"x.y.example.com","nodeDescription":"","numExecutors":"0","remoteFS":"/scratch/jenkins","labelString":"linux-disabled precise-disabled","mode":"EXCLUSIVE","":["hudson.plugins.sshslaves.SSHLauncher","hudson.slaves.RetentionStrategy$Always"],"launcher":{"stapler-class":"hudson.plugins.sshslaves.SSHLauncher","host":"x.y.example.com","credentialsId":"903329e1-fb79-4a0b-ac9d-7699266e65f6","port":"22","javaPath":"","jvmOptions":"","prefixStartSlaveCmd":"","suffixStartSlaveCmd":"","launchTimeoutSeconds":"","maxNumRetries":"0","retryWaitTime":"0"},"retentionStrategy":{"stapler-class":"hudson.slaves.RetentionStrategy$Always"},"nodeProperties":{"stapler-class-bag":"true"}}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:783)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at 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:97)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at
[JIRA] [remoting] (JENKINS-2110) # of executors field help states you can enter 0, but you cannot
Phil Miller reopened JENKINS-2110 # of executors field help states you can enter 0, but you cannot I just saw this on Jenkins LTS 1.565.3. Change By: Phil Miller (20/Feb/15 6:25 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Tim Brust commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap I do confirm that the issue is fixed in 1.599, too 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-27057) CME in WorkflowRun.logsToCopy
Jesse Glick created JENKINS-27057 CME in WorkflowRun.logsToCopy Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 20/Feb/15 6:06 PM Description: ParallelStepTest.invisibleParallelBranch observed to fail with: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.workflow.job.WorkflowRun#logsToCopy for class org.jenkinsci.plugins.workflow.job.WorkflowRun at ... Caused by: java.util.ConcurrentModificationException: null at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:394) at java.util.LinkedHashMap$EntryIterator.next(LinkedHashMap.java:413) at java.util.LinkedHashMap$EntryIterator.next(LinkedHashMap.java:412) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:75) at ... at hudson.XmlFile.write(XmlFile.java:178) at hudson.model.Run.save(Run.java:1915) at org.jenkinsci.plugins.workflow.support.steps.input.InputStepExecution.postSettlement(InputStepExecution.java:196) at org.jenkinsci.plugins.workflow.support.steps.input.InputStepExecution.proceed(InputStepExecution.java:149) at org.jenkinsci.plugins.workflow.steps.parallel.ParallelStepTest$9.evaluate(ParallelStepTest.java:360) at ... Normally Run.save would be called at the end of copyLogs, when the state is consistent, but this is coming from another thread. Possibly needs to be some kind of concurrent map. Project: Jenkins Labels: threads xstream Priority: Minor Reporter: Jesse Glick 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-27050) Parameterized seed job is automatically triggered after change
Daniel Spilker commented on JENKINS-27050 Parameterized seed job is automatically triggered after change The seed job is triggered whenever a template job changes. The idea is that you can configure a job outside of the DSL and then use that job as a template for other job with the using method. When the template changes, the seed job will re-generated all generated job. See https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-reference#using: When they are changed, the seed job will attempt to re-run, which has the side-effect of cascading changes of the template the jobs generated from it. If the template job is also created by the same seed job, the seed job will run twice. To avoid this you can use Groovy helper code to generate nearly identical jobs instead of templates. See the Jenkins Job DSL Gradle Example and some hints in the wiki here and here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27056) Latest Git Plugin breaks ghprb-plugin
Gennady Feldman created JENKINS-27056 Latest Git Plugin breaks ghprb-plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 20/Feb/15 4:27 PM Description: 2.3.5 upgrade breaks ghprb-plugin. I am seeing Null Pointer Exception in the logs referencing GhprbRepository.java which I would guess is breaking some API between the two plugins. Project: Jenkins Priority: Critical Reporter: Gennady Feldman 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-27039) User input in a stage
Yuriy Kryshchuk commented on JENKINS-27039 User input in a stage Hi Jesse, that does not work. I have created exactly this workflow: stage name: 'DevBuild', concurrency: 1 echo "doing dev build" stage name: 'Waiting to integrate' input message: 'Proceed?' stage name: 'Integration', concurrency: 1 echo "doing integration" Then I started 3 builds one after another. All three are now waiting for user input in stage "Waiting to integrate". I would expect that two earlier builds get discarded once the last one reaches the user input. Otherwise I may get many builds waiting for user interaction. 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-26582) Unexpected Executor Death - build already existed - 1.597
Jesse Glick commented on JENKINS-26582 Unexpected Executor Death - build already existed - 1.597 Deals with freestyle projects so probably distinct from JENKINS-26739. 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] [matrix-project-plugin] (JENKINS-26739) Executors are dying since 1.597 - related to the directory layout change?
Jesse Glick commented on JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? I see, the overloads of getNextBuildNumber and assignBuildNumber in MatrixConfiguration are rather dangerous. 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] [matrix-project-plugin] (JENKINS-26739) Executors are dying since 1.597 - related to the directory layout change?
Jesse Glick updated JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? Change By: Jesse Glick (20/Feb/15 4:02 PM) Component/s: matrix-project-plugin 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] [credentials-binding-plugin] (JENKINS-27040) Bound variables strip multiple dollar signs
Jesse Glick commented on JENKINS-27040 Bound variables strip multiple dollar signs Hmm, might be difficult to solve since Jenkins has a lot of complicated code for expanding variables in other variables. Possibly an issue in core rather than this plugin. Do you have a minimal reproducible test case? 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-27039) User input in a stage
Jesse Glick commented on JENKINS-27039 User input in a stage Try stage title: 'DevBuild', concurrency: 1 // do build stage title: 'Waiting to integrate' input message: 'Proceed?' stage title: 'Integration', concurrency: 1 // do integration I have not tried it yet, but I think this should allow later builds to get into the Waiting to integrate stage, so that you can agree to integrate the last one, killing the earlier ones. (The “CD” demo does not throttle the earlier stages, since it is not necessary in general, so builds only wait to enter Production when they are already approved. This is the simpler approach, but perhaps your DevBuild stage really needs to be single-threaded.) 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-27055) Slave To Master Access Control needs updating for JENKINS_HOME layout change
mwebber
commented on JENKINS-27055
Slave To Master Access Control needs updating for JENKINS_HOME layout change
The reason I think that there is an issue here, is that ${JENKINS_HOME}/secrets/filepath-filters.d/30-default.conf contains the following:
# Various plugins read/write files under build directories, so allow them all.
# - git 1.x writes changelog.xml from the slave (2.x writes from the master so need not be listed)
# - analysis-core and plugins based on it write reports to workspace-files/
# - cobertura writes coverage.xml
# - violations writes violations.xml and other content under violations/
# - dependency-check writes archive/artifacts.txt
# But not allowing deletion to prevent data loss and symlink to prevent jailbreaking.
allow create,mkdirs,read,stat,write /.+
But, it's not working for me in Jenkins 1.597+ (see JENKINS-27053) - I get
slave may not mkdirs /exports/jenkins_home/jobs/Controls_TopUp_unittests/builds/439/violations
Is /.+ correct in newer Jenkins?
I got the violations plugin to work by adding file secrets/filepath-filters.d/50-gui.conf containing this:
allow create,mkdirs,read,stat,write /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] [core] (JENKINS-27051) Create specific disable / enable job permission
Jesse Glick updated JENKINS-27051 Create specific disable / enable job permission The permission is defined by core, not a specific authorization strategy. I would be -1 on this. Enablement status is just a part of job configuration. Change By: Jesse Glick (20/Feb/15 3:48 PM) Labels: permissions Assignee: Jesse Glick Component/s: core Component/s: matrix-auth-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] [core] (JENKINS-27055) Slave To Master Access Control needs updating for JENKINS_HOME layout change
mwebber created JENKINS-27055 Slave To Master Access Control needs updating for JENKINS_HOME layout change Issue Type: Bug Assignee: Unassigned Components: core Created: 20/Feb/15 3:39 PM Description: If you look on the wiki describing the Slave To Master Access Control, there is a section on File access rules, where it says: can be used as a prefix to match your build record directory, such as /var/lib/jenkins/job/foo/builds/2014-10-17_12-34-56 However, Jenkins versions after 1.597 have a different home directory structure (see JENKINS-24380). The wiki page for Slave To Master Access Control reflects the old layout. Can someone confirm (or otherwise) that the token works in Jenkins both before and after 1.597, and update the wiki accordingly? Project: Jenkins Priority: Critical Reporter: mwebber 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] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a
Paul Fee
created JENKINS-27054
Radio buttons would be easier to click if associated text was part of a
Issue Type:
Improvement
Assignee:
stevengbrown
Components:
timestamper-plugin
Created:
20/Feb/15 3:38 PM
Description:
When viewing console log of a job, the timestamper plugin adds three timestamp options:
System clock time
Elapsed time
None
The text is not clickable, only the radio buttons can be used to make a choice.
It would be nice if the text was associated with the radio button.
The HTML comes from timestamper-plugin/src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/usersettings.jelly
${%System clock time}
${%Elapsed time}
${%None}
The tag does not need a tag. Embedding the within a will allow the text be associated with the radio button.
Suggested code:
${%System clock time}
${%Elapsed time}
${%None}
Environment:
Jenkins installed from Fedora 21 package.
Jenkins version: 1.590
Timestamper plugin: 1.5.15
Project:
Jenkins
Labels:
user-experience
Priority:
Minor
Reporter:
Paul Fee
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-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
SCM/JIRA link daemon commented on JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Code changed in jenkins User: James Nord Path: src/main/java/hudson/remoting/AtmostOneThreadExecutor.java src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/PingThread.java src/main/java/hudson/remoting/Request.java src/main/java/hudson/remoting/SingleLaneExecutorService.java src/main/java/hudson/remoting/SynchronousExecutorService.java http://jenkins-ci.org/commit/remoting/75fb3559e354418000760573eac19efcd86c267f Log: JENKINS-21251 Initial calculation of wait time was susseptable to clock drift. The calculation on how long to wait in various places on the code was suseptable to the clock changing as multiple calls where made to System.currentTimeMillis() for the initial calculation. Changed this so that we use a single call to System.nanoTime and made just a single call for the initial calculation. There is still a potential issue for any callers of Channel.getLastHeard() this will be addressed in a future change and has only been noted in this commit. 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-27052) It is possible to have multiple instances of a workflow in the same stage, even with `concurrency:1`
Jesse Glick
updated JENKINS-27052
It is possible to have multiple instances of a workflow in the same stage, even with `concurrency:1`
Change By:
Jesse Glick
(20/Feb/15 3:20 PM)
Description:
I manage to create a simple workflow that can show that the
`
{{
concurrency:1
`
}}
on stages has an issue:
```
{code}
import java.util.Randomdef waiter(max) { def rand = new Random() def time = rand.nextInt(Integer.parseInt("${max}")+1) echo "Waiting for ${time} seconds..." sh "sleep ${time}s" echo "You get served.."}stage name:'build', concurrency: 1node { waiter(10) }stage name:'concurrent', concurrency:1node { waiter(20) }stage name: 'deploy', concurrency: 1node { waiter(30) }
```
{code}
To reproduce it: 1. Launch 2 instances of the workflow. The first will start, the second will wait the first one to leave the stage build. 2. When the first one leave the stage build, start a new instance of the workflowThe third instance will not wait the second instance to leave the stage build before starting.
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
SCM/JIRA link daemon commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Code changed in jenkins User: Tom Fennelly Path: core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/model/Run.java core/src/main/java/hudson/model/queue/WorkUnit.java test/src/test/java/hudson/model/QueueTest.java test/src/test/resources/hudson/model/QueueTest/recover_from_legacy_list.zip http://jenkins-ci.org/commit/jenkins/e88bf5694b7f64c833cc991447d511a964c10683 Log: Merge pull request #1566 from tfennelly/JENKINS-26445 Permanently valid Queue.Item.id Compare: https://github.com/jenkinsci/jenkins/compare/419d670cd0f6...e88bf5694b7f 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] [violations-plugin] (JENKINS-27053) Violations plugin incompatible with Slave To Master Access Control
mwebber created JENKINS-27053 Violations plugin incompatible with Slave To Master Access Control Issue Type: Bug Assignee: peterkittreilly Components: violations-plugin Created: 20/Feb/15 3:07 PM Description: I have the Violations Plugin (0.7.11 - the latest) installed on Jenkins 1.599, and recently turned on Slave To Master Access Control (desribed on the Jenkins wiki). This resulted in a job getting the exception detailed below. This suggetsts that an update is required for the Violations plugin. ERROR: Build step failed with exception java.lang.SecurityException: slave may not mkdirs /exports/jenkins_home/jobs/Controls_TopUp_unittests/builds/439/violations See http://jenkins-ci.org/security-144 for more details at jenkins.SoloFilePathFilter.noFalse(SoloFilePathFilter.java:31) at jenkins.SoloFilePathFilter.mkdirs(SoloFilePathFilter.java:52) at hudson.FilePath.mkdirs(FilePath.java:2876) at hudson.FilePath.access$800(FilePath.java:191) at hudson.FilePath$36.invoke(FilePath.java:1885) at hudson.FilePath$36.invoke(FilePath.java:1881) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) 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 org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to channel(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) at hudson.FilePath.act(FilePath.java:978) at hudson.FilePath.act(FilePath.java:967) at hudson.FilePath.write(FilePath.java:1881) at hudson.plugins.violations.generate.ExecuteFilePath.execute(ExecuteFilePath.java:40) at hudson.plugins.violations.generate.GenerateXML.execute(GenerateXML.java:40) at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:122) at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:25) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) 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.run(FutureTask.java:262) 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:745) at ..remote call to controls_rhel6(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) at hudson.FilePath.act(FilePath.java:978) at hudson.FilePath.act(FilePath.java:967) at hudson.plugins.violations.ViolationsPublisher.perform(ViolationsPublisher.java:74) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1743) at hudson.
[JIRA] [bitbucket-plugin] (JENKINS-26805) Job is not triggered after merging a branch
Dominik Bartholdi commented on JENKINS-26805 Job is not triggered after merging a branch when will this fix be released? 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] [display-upstream-changes-plugin] (JENKINS-27048) Multiple upstream projects
Rob Petti assigned JENKINS-27048 to Unassigned Multiple upstream projects Change By: Rob Petti (20/Feb/15 2:33 PM) Assignee: Rob Petti 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-27052) It is possible to have multiple instances of a workflow in the same stage, even with `concurrency:1`
Adrien Lecharpentier
created JENKINS-27052
It is possible to have multiple instances of a workflow in the same stage, even with `concurrency:1`
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
20/Feb/15 2:27 PM
Description:
I manage to create a simple workflow that can show that the `concurrency:1` on stages has an issue:
```
import java.util.Random
def waiter(max) {
def rand = new Random()
def time = rand.nextInt(Integer.parseInt("${max}")+1)
echo "Waiting for ${time} seconds..."
sh "sleep ${time}s"
echo "You get served.."
}
stage name:'build', concurrency: 1
node { waiter(10) }
stage name:'concurrent', concurrency:1
node { waiter(20) }
stage name: 'deploy', concurrency: 1
node { waiter(30) }
```
To reproduce it:
1. Launch 2 instances of the workflow. The first will start, the second will wait the first one to leave the stage build.
2. When the first one leave the stage build, start a new instance of the workflow
The third instance will not wait the second instance to leave the stage build before starting.
Project:
Jenkins
Priority:
Major
Reporter:
Adrien Lecharpentier
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] [matrix-auth-plugin] (JENKINS-27051) Create specific disable / enable job permission
Oscar Picasso created JENKINS-27051 Create specific disable / enable job permission Issue Type: New Feature Assignee: Jesse Glick Components: matrix-auth-plugin Created: 20/Feb/15 2:25 PM Description: Currently in order to enable or disable a job, a user must have Job Configure permissions in the Matrix-based security configuration. We would like to be able to manage the enable / disable job permission independently from the job configure permission. Project: Jenkins Priority: Minor Reporter: Oscar Picasso 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-27050) Parameterized seed job is automatically triggered after change
Christoph Burgmer created JENKINS-27050 Parameterized seed job is automatically triggered after change Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 20/Feb/15 1:55 PM Description: We have setup the seed job to take parameters on build so that we are able to generate several job pipelines of the same type. (Background: we have a similar pipeline for all micro services and our seed job is able to spin up a pipeline for a new micro service in one step.) When changing the seed job's config and manually running a new build another build is automatically triggered on top with "Template has changed" given as build cause. This automatic build takes no manual user input and thus creates a new job setup with the default values provided for the parameters. This results in unwanted jobs on Jenkins. We have deselected "Ignore changes" as we do want a new run to update existing jobs, albeit only for the parametrized setup (and not for any other clones). It looks like setting "Ignore changes" to true does not trigger the issue, but this is not a viable solution in our case. Our current workaround is to detect those "ghost" builds with cause "Template has changed" via a quick shell step inside the seed job: set -e curl $BUILD_URL/api/json | grep -v "Template has changed" This will cause the automatic build to fail, while manually triggered builds pass. For us this is not viable solution in the long term. As far as we understand this is caused by https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/MonitorTemplateJobs.java#L83 although we do not understand what the intentions are. The job itself has no trigger configured under "Build Triggers" and as such we do not expect builds to be triggered automatically. Environment: Jenkins 1.580.2 Job DSL 1.28 Project: Jenkins Priority: Major Reporter: Christoph Burgmer 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] [pegdown-formatter-plugin] (JENKINS-27049) PegDown formatter causes deprecation message in jenkins log
Mark Waite created JENKINS-27049 PegDown formatter causes deprecation message in jenkins log Issue Type: Bug Assignee: bap Components: pegdown-formatter-plugin Created: 20/Feb/15 1:35 PM Description: When the PegDown formatter is running in Jenkins 1.580.3, a message is written to the Jenkins log (/var/log/jenkins/jenkins.log on my Ubuntu 14.04 server) which says: WARNING: 'stapler-class' is deprecated: org.jenkins_ci.plugins.pegdown_formatter.PegDownFormatter Another message is written a little earlier in the log which says: WARNING: 'stapler-class' is deprecated: hudson.security.PAMSecurityRealm The warning does not seem to cause any harm to functionality Environment: Jenkins 1.580.3 PegDown formatter 1.3 Project: Jenkins Priority: Trivial Reporter: Mark Waite 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] [m2release-plugin] (JENKINS-15298) Default versioning mode is not getting picked while invoking the maven release build
Guy Rooms commented on JENKINS-15298 Default versioning mode is not getting picked while invoking the maven release build Same problem here on: jenkins: 1.564 Maven release plugin: 0.14.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pegdown-formatter-plugin] (JENKINS-27049) PegDown formatter causes deprecation message in jenkins log
Mark Waite updated JENKINS-27049 PegDown formatter causes deprecation message in jenkins log Change By: Mark Waite (20/Feb/15 1:36 PM) Environment: Jenkins 1. 580.3 599 PegDown formatter 1.3 Description: When the PegDown formatter is running in Jenkins 1. 580.3 599 , a message is written to the Jenkins log (/var/log/jenkins/jenkins.log on my Ubuntu 14.04 server) which says:WARNING: 'stapler-class' is deprecated: org.jenkins_ci.plugins.pegdown_formatter.PegDownFormatterAnother message is written a little earlier in the log which says:WARNING: 'stapler-class' is deprecated: hudson.security.PAMSecurityRealmThe warning does not seem to cause any harm to functionality 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] [pegdown-formatter-plugin] (JENKINS-27049) PegDown formatter causes deprecation message in jenkins log
Mark Waite updated JENKINS-27049 PegDown formatter causes deprecation message in jenkins log Change By: Mark Waite (20/Feb/15 1:38 PM) Description: When the PegDown formatter is running in Jenkins 1.599, a message is written to the Jenkins log (/var/log/jenkins/jenkins.log on my Ubuntu 14.04 server) which says:WARNING: 'stapler-class' is deprecated: org.jenkins_ci.plugins.pegdown_formatter.PegDownFormatterAnother message is written a little earlier in the log which says:WARNING: 'stapler-class' is deprecated: hudson.security.PAMSecurityRealmThe warning does not seem to cause any harm to functionality . The warning does not appear in Jenkins 1.580.3 log files, only in the more recent 1.599 log file. 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] [display-upstream-changes-plugin] (JENKINS-27048) Multiple upstream projects
Maxim Nikolaev created JENKINS-27048 Multiple upstream projects Issue Type: New Feature Assignee: Rob Petti Attachments: snapshot3.png Components: display-upstream-changes-plugin Created: 20/Feb/15 1:19 PM Description: Consider a job (downstream job) that watches several other jobs (upstream jobs) and is triggered when anyone of them succeeds. Then the downstream job goes into quiet period. During that period upstream jobs finish up multiple times and later Jenkins shows all triggered upstream jobs inside downstream job build info. Now display-upstream-changes-plugin doesn't show changes from multiple upstream projects - only from the first one. My current workaround for this is to construct artifacts with redmine issue numbers and scm hashes with help of downstream job rather than seeing that info on it's changes page extended with this plugin. I've attached screenshot with example. Project: Jenkins Priority: Minor Reporter: Maxim Nikolaev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26993) GIT Plugin requires /tmp to be executable
Mark Waite closed JENKINS-26993 as Won't Fix GIT Plugin requires /tmp to be executable Change By: Mark Waite (20/Feb/15 1:14 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26993) GIT Plugin requires /tmp to be executable
Mark Waite resolved JENKINS-26993 as Won't Fix GIT Plugin requires /tmp to be executable Change By: Mark Waite (20/Feb/15 1:14 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Mark Waite commented on JENKINS-26757 "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs I confirmed with git client plugin 1.16.1 and git plugin 2.3.5 that a private bitbucket repository with embedded user name and password fails to fetch. The remote.origin.url is correctly set in the workspace repository and is usable by "git remote update". If I login to that slave, change directory to that repository and perform a "git remote update origin", the changes are fetched into the repository from the bitbucket URL. I think that shows the problem is specific to a private bitbucket repository with https protocol and embedded user name and password from a Jenkins job. Change any one of those items (for example, use a credential instead of embedding the user name/password, or use a public bitbucket repository, or use a different protocol) and it seems to work. I realize none of those alternatives meet the needs of Flavio Donzé, but I now better understand the symptoms of the 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] [git-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Mark Waite edited a comment on JENKINS-26757 "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs I confirmed with git client plugin 1.16.1 and git plugin 2.3.5 that a private bitbucket repository with embedded user name and password fails to fetch. The remote.origin.url is correctly set in the workspace repository and is usable by "git remote update". If I login to that slave, change directory to that repository and perform a "git remote update origin", the changes are fetched into the repository from the bitbucket URL. I think that shows the problem is specific to a private bitbucket repository with https protocol and embedded user name and password from a Jenkins job. Change any one of those items (for example, use a credential instead of embedding the user name/password, or use a public bitbucket repository, or use a different protocol) and it seems to work. I realize none of those alternatives meet the needs of Flavio Donzé, but I now better understand the symptoms of the 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] [git-client-plugin] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Mark Waite updated JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git Change By: Mark Waite (20/Feb/15 1:01 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Mark Waite edited a comment on JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git The git-client-plugin 1.14.0 change to remove the call to JGit implementation of checkCredentials resolved this issue for me. I can clone from https://markewa...@bitbucket.org/markewaite/bin.git, a private bitbucket repository using stored credentials as reported in JENKINS-22694. With git plugin 2.3.5 and git client plugin 1.16.1, I cannot access a private bitbucket repository when the user name and password are embedded in the https URL. Refer to JENKINS-26757 for what appears to be a duplicate report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Mark Waite reopened JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git Change By: Mark Waite (20/Feb/15 12:59 PM) Resolution: Fixed Status: Closed Reopened 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] [jenkins-tag-cloud] (JENKINS-26237) java.io.IOException
Nikolaj Hestbek commented on JENKINS-26237 java.io.IOException I see the exact same issue on Jenkins ver. 1.594 I did a new item using "Copy existing Item". Each time I try to save a change in the new job (which should be a exact copy of the old except the name) I get the error Vikas Goyal reports. The original job does not have any 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.
