| I am running Jenkins 2.19.3 with all plugins up-to-date as of today (19/11/2016). The workflow-basic-steps plugin in particular is at v2.3. I'm using a waitUntil step to wait for other builds to finish (code here: https://github.com/doudou/autoproj-jenkins/blob/master/lib/autoproj/jenkins/templates/library.pipeline.erb#L104) In some cases, it works as expected. The callback is called a few times and the job's console output displays the retry time
[Pipeline] stage
[Pipeline] { (waiting for upstream jobs to finish)
[Pipeline] echo
upstream build: base-cmake#6
[Pipeline] waitUntil
[Pipeline] {
[Pipeline] echo
waiting for job base-cmake#6 to finish
[Pipeline] }
Will try again after 0.25 sec
[Pipeline] {
[Pipeline] echo
waiting for job base-cmake#6 to finish
[Pipeline] }
Will try again after 0.3 sec
[Pipeline] {
[Pipeline] echo
waiting for job base-cmake#6 to finish
[Pipeline] }
Will try again after 0.36 sec
However, in quite a few cases, the waitUntil block returns but then ... nothing. The build disappears from the build queue, but is still marked as active when looking at the job page (its status still "blinks") The console output shows that the waitUntil block does return, but no "Try again" message anymore. It just hangs there.
[Pipeline] stage
[Pipeline] { (waiting for upstream jobs to finish)
[Pipeline] echo
upstream build: base-types#3
[Pipeline] echo
upstream build: base-eigen#3
[Pipeline] echo
upstream build: base-cmake#6
[Pipeline] echo
upstream build: base-logging#3
[Pipeline] echo
upstream build: external-sisl#3
[Pipeline] echo
upstream build: gui-vizkit3d#3
[Pipeline] waitUntil
[Pipeline] {
[Pipeline] echo
waiting for job base-types#3 to finish
[Pipeline] }
|
