[JIRA] [build-flow] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Avner Tamir created JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 27/Apr/14 10:13 AM Description: After upgrading to latest build-flow plugin version (0.11.1) we've found that most post build actions doesn't work, for example triggering projects, groovy post-build, email notification, etc. Also SCM polling wasn't working. When rolling back to 0.10 everything works fine Thanks, Avner Tamir Project: Jenkins Labels: plugin Priority: Major Reporter: Avner Tamir 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-tracker] (JENKINS-22714) all slaves are terminated when javaw is stopped on one slave
ziv SHAPIRA updated JENKINS-22714 all slaves are terminated when javaw is stopped on one slave Change By: ziv SHAPIRA (27/Apr/14 10:48 AM) Description: When I ran Java update on a slave, it requested that javaw is stopped.when approving that ALL the slaves were terminated. I am adding the error in the server log for one of the slaves.The slaves pages also display a "failed to abort" error (pic attached) and cannot be restarted using javaw, before the whole Jenkins server (the service, not the machine) is restarted. slaves are VM's that are hosted on VMWARE server I also noticed that when a VM is restarted, this terminates all others (by Jenkins server) version: 1.560--WARNING: NioChannelHub keys=17 gen=201082: Computer.threadPoolForRemoting [#2] for + HV1-VM-SLAVE-22 terminatedjava.io.IOException: Failed to abortat org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:184)at org.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:599)at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:481)at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)at java.util.concurrent.FutureTask.run(FutureTask.java:138)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)at java.lang.Thread.run(Thread.java:662)Caused by: java.nio.channels.ClosedChannelExceptionat sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:663)at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:430)at org.jenkinsci.remoting.nio.Closeables$1.close(Closeables.java:20)at org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport.closeR(NioChannelHub.java:289)at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:226)at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:224)at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:474)... 7 moreApr 22, 2014 8:56:08 AM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed 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] (JENKINS-22780) pushing a new branch doe snot trigger a build
Dominik Bartholdi created JENKINS-22780 pushing a new branch doe snot trigger a build Issue Type: Bug Assignee: Nicolas De Loof Components: bitbucket Created: 27/Apr/14 11:51 AM Description: even though I have the "Branch Specifier" set to "/feature/", when I push a new branch to e.g. origin/feature/myNewBranch no new build is triggered. Project: Jenkins Priority: Major Reporter: Dominik Bartholdi 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] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin
Michal Turek started work on JENKINS-22761 Missing links to source in cppcheck plugin Change By: Michal Turek (27/Apr/14 2:37 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] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Jens Brejner commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Hi. Yes, the key issue is the combination of "polling requires workspace" and "no slave exists". I have been tied to other tasks the last couple of days, but will write a fix 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] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin
Michal Turek commented on JENKINS-22761 Missing links to source in cppcheck plugin Ok, I understand now. You probably execute Cppcheck from a sub-directory of the workspace, but the plugin expects all paths in the report are relative to the workspace. I have just added "Report in a sub-directory of the workspace (advanced)" section to the plugin wiki, there are two possible solutions to your problem. Please let me know if such help is sufficient for you, I will reject the task in such 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] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
SCM/JIRA link daemon commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitProcessor.java http://jenkins-ci.org/commit/xunit-plugin/531de4bb33d769c33d91a4547fc5322ca026f238 Log: Merge pull request #21 from lanfeust69/master Fix JENKINS-18443 when running on slaves Compare: https://github.com/jenkinsci/xunit-plugin/compare/be6f3ecc808d...531de4bb33d7 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] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
SCM/JIRA link daemon commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Code changed in jenkins User: Jean-Jacques Lafay Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitProcessor.java http://jenkins-ci.org/commit/xunit-plugin/bfbd152110312588b99d20a0f94305c8c07cd02c Log: Fix JENKINS-18443 when running on slaves 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-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1
Daniel Beck resolved JENKINS-22328 as Duplicate ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1 Duplicates JENKINS-22710, will be fixed in 1.562. Change By: Daniel Beck (27/Apr/14 9:43 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1
Daniel Beck updated JENKINS-22328 ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1 Change By: Daniel Beck (27/Apr/14 9:43 PM) Component/s: core Component/s: debian-package-builder 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-22710) Broken Debian upgrades because postinst doesn't check for present group/user
Daniel Beck resolved JENKINS-22710 as Fixed Broken Debian upgrades because postinst doesn't check for present group/user Fix will be in 1.561. Michael: The bot picks up the status change only if you write something like [FIXED JENKINS-22710] as commit message. Change By: Daniel Beck (27/Apr/14 9:55 PM) 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.
