-
Bug
-
Resolution: Not A Defect
-
Major
-
None
This issue appears when using the "Trigger/Call builds on another project" item and the trigger is configured with the "Block until the triggered projects finish their builds" enabled.
When an Administrator has requested Jenkins to shut down, any newly triggered build will be pending until Jenkins shuts down.
However, when build A triggers another build B, and build A is configured to wait for build B to finish in order to continue there is to following issue. The build B will be pending forever waiting for Jenkins to shut down, BUT the build A will be in progress forever, and Jenkins will be waiting for build A to finish before it can shut down. Hence a deadlock.
Potential solutions:
- Jenkins should abort all pending jobs
- Jenkins should not block the pending jobs for running and only shut down when there is a time window