-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins ver. 1.610
workflow-plugin 1.5
When two workflow jobs try to trigger the same job at the same time, java.hudson.model.Queue#scheduleInternal may detect a duplicate.
When that happens, a second instance of WaitingItem does not get created, meaning one of the workflow runs will have no listeners related to the triggered job.
When the triggered job ends, only one workflow run will be notified and continue, the other one will stay listening forever.
The workaround I've had to apply to deal with this is running the following in scriptler:
Jenkins.instance.getItemByFullName(jobName)
.builds.findAll
.each{it.execution.currentExecutions.get()
.each
}
- is blocking
-
JENKINS-25550 Hard kill
-
- Resolved
-
- is duplicated by
-
JENKINS-34201 Pipeline plugin can't handle large numbers of parallel build jobs
-
- Resolved
-
- links to
[JENKINS-28063] Triggering the same job twice results in zombie workflow run
Link |
New:
This issue is blocking |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR 121 (Web Link)" [ 12807 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 162666 ] | New: JNJira + In-Review [ 197025 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Link |
New:
This issue is duplicated by |
Link |
Original:
This issue is related to |