-
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
-
There is a known issue if the child jobs have "block if upstream is running" enabled as they see the triggering job as running, which might be the issue that you are seeing.
You should check, that there is a free executor for the child project to run on matching its labels, etc. If this is not the case, can you actually post the reasons that the pending jobs are not running (from the tooltip when hovering over the items in the Queue), as this will normally indicate the reason for the builds not running.
i.e. waiting for an Executor on slave1 or Waiting for Up/Downstream project to finish
Can you provide the following:
Plugins(+versions) that are used in the parent and child jobs including the parameterized-trigger.
and also attach the config.xml files to the issue for the two jobs. (suitably cleansed od sensitive data)
And if you are are building on the slaves can you also indicate the master/slave config
i.e. linux master with 0 executors, slave1 windows with 2 executors that these jobs are tied to.
So that others can reproduce the issue and allow for it to be debugged.