-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins version 1.427
We have a project (parent) with multiple steps, one of the step being configured as 'trigger/call a build on other projects' (i.e, child job)
We have selected the option 'block until the triggered projects finish their builds', so that Parent project will be on hold until the child project gets completed.
It works fine if we run the parent project one time.
But, if we run another instance of the same Parent project, the child project run (triggered from first run), goes into 'pending forever' state.
Similarly, the second Parent project run also goes to 'pending forever'
Please let us know if there is any fix/workaround.
===========
The projects are configured as:
Parent Project:-
-Step 1 (Some commands)
-Step 2 (Invoke a “Child” project) – parent has to be in wait state until the child completes
-Step 3 (Some commands)
Child Project:-
-Step 1 (Some Commands)
================
Regards
Satya
- is related to
-
JENKINS-19776 Deadlock of AsyncFutureImpl.get() during massive submission of distributed jobs
- Resolved
-
JENKINS-21932 Job hangs if one of multiple triggered builds was aborted
- Resolved