[JIRA] (JENKINS-10102) site-deploy failed with "java.io.IOException: Pipe is already closed"
H.-Dirk Schmitt commented on JENKINS-10102 site-deploy failed with "java.io.IOException: Pipe is already closed" Bug hasn't vanished. It is still in 1.492 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
[JIRA] (JENKINS-10102) site-deploy failed with "java.io.IOException: Pipe is already closed"
H.-Dirk Schmitt edited a comment on JENKINS-10102 site-deploy failed with "java.io.IOException: Pipe is already closed" Bug hasn't vanished. It is still in 1.492 below ubuntu 12.04 and openjdk-7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10102) site-deploy failed with "java.io.IOException: Pipe is already closed"
H.-Dirk Schmitt commented on JENKINS-10102 site-deploy failed with "java.io.IOException: Pipe is already closed" If I delete ${JENKINS_HOME}/jobs/MYJOB/site, the next build is successful. But the next invocation run again in this problem. 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
[JIRA] (JENKINS-16575) SEVERE: Failed to record SCM polling - java.lang.NullPointerException
H.-Dirk Schmitt created JENKINS-16575 SEVERE: Failed to record SCM polling - java.lang.NullPointerException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 31/Jan/13 4:41 PM Description: After updating jenkins the notification of jenkins vi Subversion post commit hook has become broken. The syslog shows: Jan 31 16:37:16 garfield jenkins: SEVERE: Failed to record SCM polling for hudson.maven.MavenModuleSet@a2ce5c5[bvopmenu-common] Jan 31 16:37:16 garfield jenkins: java.lang.NullPointerException Jan 31 16:37:16 garfield jenkins: #011at java.util.TreeMap.putAll(TreeMap.java:308) Jan 31 16:37:16 garfield jenkins: #011at org.jenkinsci.plugins.envinject.EnvInjectVarList.(EnvInjectVarList.java:25) Jan 31 16:37:16 garfield jenkins: #011at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.getTarget(EnvInjectPluginAction.java:20) Jan 31 16:37:16 garfield jenkins: #011at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.buildEnvVars(EnvInjectPluginAction.java:24) Jan 31 16:37:16 garfield jenkins: #011at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:948) Jan 31 16:37:16 garfield jenkins: #011at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:59) Jan 31 16:37:16 garfield jenkins: #011at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:154) Jan 31 16:37:16 garfield jenkins: #011at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1230) Jan 31 16:37:16 garfield jenkins: #011at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) Jan 31 16:37:16 garfield jenkins: #011at hudson.scm.SCM.poll(SCM.java:373) Jan 31 16:37:16 garfield jenkins: #011at hudson.model.AbstractProject._poll(AbstractProject.java:1493) Jan 31 16:37:16 garfield jenkins: #011at hudson.model.AbstractProject.poll(AbstractProject.java:1410) Jan 31 16:37:16 garfield jenkins: #011at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) Jan 31 16:37:16 garfield jenkins: #011at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) Jan 31 16:37:16 garfield jenkins: #011at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) Jan 31 16:37:16 garfield jenkins: #011at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) Jan 31 16:37:16 garfield jenkins: #011at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) Jan 31 16:37:16 garfield jenkins: #011at java.util.concurrent.FutureTask.run(FutureTask.java:166) Jan 31 16:37:16 garfield jenkins: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) Jan 31 16:37:16 garfield jenkins: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) Jan 31 16:37:16 garfield jenkins: #011at java.lang.Thread.run(Thread.java:722) Environment: jenkins V 1.500 Project: Jenkins Priority: Blocker Reporter: H.-Dirk Schmitt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16575) SEVERE: Failed to record SCM polling - java.lang.NullPointerException
H.-Dirk Schmitt commented on JENKINS-16575 SEVERE: Failed to record SCM polling - java.lang.NullPointerException revert EnvInject plugin from 1.81 to 1.80 resolves the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16575) SEVERE: Failed to record SCM polling - java.lang.NullPointerException
H.-Dirk Schmitt updated JENKINS-16575 SEVERE: Failed to record SCM polling - java.lang.NullPointerException Change By: H.-Dirk Schmitt (31/Jan/13 5:57 PM) Component/s: 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/groups/opt_out.
[JIRA] (JENKINS-16575) SEVERE: Failed to record SCM polling - java.lang.NullPointerException - EnvInject Plugin
H.-Dirk Schmitt updated JENKINS-16575 SEVERE: Failed to record SCM polling - java.lang.NullPointerException - EnvInject Plugin Change By: H.-Dirk Schmitt (31/Jan/13 5:58 PM) Summary: SEVERE: Failed to record SCM polling - java.lang.NullPointerException - EnvInject 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/groups/opt_out.
[JIRA] (JENKINS-16575) SEVERE: Failed to record SCM polling - java.lang.NullPointerException - EnvInject Plugin
H.-Dirk Schmitt updated JENKINS-16575 SEVERE: Failed to record SCM polling - java.lang.NullPointerException - EnvInject Plugin Change By: H.-Dirk Schmitt (31/Jan/13 5:59 PM) Component/s: envinject Component/s: 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/groups/opt_out.
[JIRA] (JENKINS-10102) site-deploy failed with "java.io.IOException: Pipe is already closed"
H.-Dirk Schmitt commented on JENKINS-10102 site-deploy failed with "java.io.IOException: Pipe is already closed" still in 1.500 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10102) site-deploy failed with "java.io.IOException: Pipe is already closed"
H.-Dirk Schmitt updated JENKINS-10102 site-deploy failed with "java.io.IOException: Pipe is already closed" Change By: H.-Dirk Schmitt (31/Jan/13 6:09 PM) 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/groups/opt_out.
[JIRA] (JENKINS-10102) site-deploy failed with "java.io.IOException: Pipe is already closed"
H.-Dirk Schmitt commented on JENKINS-10102 site-deploy failed with "java.io.IOException: Pipe is already closed" Possible workaround, add pre-build step: rm -rf ${JENKINS_HOME}/jobs/${JOB_NAME}/site This work if the build is done on the master node, but is failing if the build is done on a slave node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-15936) ajax menus not working below chromium
H.-Dirk Schmitt commented on JENKINS-15936 ajax menus not working below chromium Seems to work 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/groups/opt_out.