Re: Builds fail randomly without reason given
Hello, Just to specify, the triggered builds mentioned above are MultiPhase jobs so it may be an issue with that plug-in. I linked to another post https://groups.google.com/forum/#!topic/jenkinsci-users/vva7-dLYQL4 of mine above which describes a similar problem and someone just replied with the following hypothesis: This appears to be an issue using the MultiPhase job plugin + Allow Concurrent Builds + restrict where this job can be run /David On Wednesday, August 20, 2014 3:05:30 PM UTC+2, David tha Dude wrote: Hello, We use DSL in a Build Flow project to trigger around 50 parallel builds on 2 slave nodes. However, some of the triggered jobs fail for no apparent reason. The only message in the Jenkins log file is: Aug 20, 2014 12:38:41 AM hudson.model.Run execute INFO: my_triggered_build_name #9288 main build action completed: FAILURE The log message inside the failed triggered builds indicates that execution failed at the first action which is some simple shell command. The nodes are not under high load. The build will be successful when re-launched manually. I have posted about a similar issue before https://groups.google.com/forum/#!topic/jenkinsci-users/vva7-dLYQL4. Has anyone experienced similar issues? What can be done to fix/work around the problem. I would also appreciate hints as to what we can do to make error logging more verbose. The lack of information makes the issue nearly impossible to debug. Thank you, /David -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Builds fail randomly without reason given
Hello, We use DSL in a Build Flow project to trigger around 50 parallel builds on 2 slave nodes. However, some of the triggered jobs fail for no apparent reason. The only message in the Jenkins log file is: Aug 20, 2014 12:38:41 AM hudson.model.Run execute INFO: my_triggered_build_name #9288 main build action completed: FAILURE The log message inside the failed triggered builds indicates that execution failed at the first action which is some simple shell command. The nodes are not under high load. The build will be successful when re-launched manually. I have posted about a similar issue before https://groups.google.com/forum/#!topic/jenkinsci-users/vva7-dLYQL4. Has anyone experienced similar issues? What can be done to fix/work around the problem. I would also appreciate hints as to what we can do to make error logging more verbose. The lack of information makes the issue nearly impossible to debug. Thank you, /David -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins silently skipping MultiJob phase.
Hello, We trigger a parallel batch of roughly 30 parametrized MultiJobs. The triggering job and each of the phases of the MultiJob can run on one of 2 slave nodes. This is specified via the Restrict where this job can run option. About 1 in 15 times a phase (mostly the first one) of the MultiJob is silently skipped. Jenkins simply states Not Built next to the job phase, that's it - the next phase proceeds even though according to the job setup it should only execute if the previous phase was successful. I find this unsettling. Has anyone experienced similar issues? If so, how can they be resolved. Thanks, Regards, /David -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Failure to trigger builds on nodes sharing a label.
Hello, I cannot seem to trigger jobs to run on several nodes using the Node Label Parameter Plug-In. See this JIRAhttps://issues.jenkins-ci.org/browse/JENKINS-22185for more details. Has anybody else experienced this issue? What other techniques are there to trigger builds on all nodes sharing a label? Thank you, /David -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
