-
Bug
-
Resolution: Postponed
-
Major
-
None
-
jenkins 1.593
multijob plugin 1.16
With a job configuration like:
parent_job:
child_job
child_job
occasionally we'll get output that looks like this:
Starting build job child_job.
Starting build job child_job.
Finished Build : #123 - Job : child_job with status : SUCCESS
<this hangs forever, so we abort the parent_job>
Aborting all subjobs.
Finished Build : #124 - Job : child_job with status : ABORTED
However, job #124 will always have finished successfully. We see this relatively rarely (~5% of parent_job builds?). My guess is that there's a race condition causing this, since we usually see this during times of high load (ie many child_job instances are being started).
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- links to
[JENKINS-27371] Parent builds sometimes hang on successful child builds of same type
Simon Weber
added a comment - We haven't seen this issue in a few months. We're now running Jenkins 1.628, trigger plugin 2.27, and multijob from source at https://github.com/jenkinsci/tikal-multijob-plugin/pull/65.
Simon Weber
added a comment - We haven't seen this issue in a few months. We're now running Jenkins 1.628, trigger plugin 2.27, and multijob from source at https://github.com/jenkinsci/tikal-multijob-plugin/pull/65 . 
Tony Bridges
added a comment - We've seen this a few times, most recently in a MultiJob run calling a maven job, but previously in a Freestyle job calling maven jobs.
We are running 1.609.3.1, CBE.
I've opened a ticket with CB Support and cited this defect.
Tony Bridges
added a comment - We've seen this a few times, most recently in a MultiJob run calling a maven job, but previously in a Freestyle job calling maven jobs.
We are running 1.609.3.1, CBE.
I've opened a ticket with CB Support and cited this defect. Tony Bridges
added a comment - Does the pull request conclusively correct the issue ? If so, maybe we can get it rolled into a new plugin release ?
Tony Bridges
added a comment - Does the pull request conclusively correct the issue ? If so, maybe we can get it rolled into a new plugin release ? Simon Weber
added a comment - tbridges I don't think this was solved for us until I upgraded Jenkins. I'm not sure what combination of the jenkins, trigger plugin, and multijob plugin upgrades is necessary to solve it, but the environment I described earlier has been rock solid for months now.
Simon Weber
added a comment - tbridges I don't think this was solved for us until I upgraded Jenkins. I'm not sure what combination of the jenkins, trigger plugin, and multijob plugin upgrades is necessary to solve it, but the environment I described earlier has been rock solid for months now. How to reproduce it:
- Configure a FreeStyle Project - freeStyle01
- Configure a Maven Project - maven01
- Configure a Multijob Project with 30 subjobs (enough to have time to stop slave agent) - Multijob01
- Configure one slave agent with 1 executor - slave01
- Run Multijob01
- Go to Manage Jenkins/Manage Nodes and put slave01 offline or kill "java -jar slave.jar" on slave agent
- Multijob01 hang waiting for finish task
So I would think this could happen even with a slight disconnect of the slave per Ivan's last comment.
Is there any more information that can be provided here?
Closing issue as part of tikal-multijob-plugin issues cleanup.
If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)
I can recreate when using https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin