-
Improvement
-
Resolution: Fixed
-
Major
-
None
build should have an option to not wait for the downstream build to complete.
- is related to
-
JENKINS-27127 wait/notify steps
-
- Open
-
-
JENKINS-27096 Map Queue.Item.id onto Run
-
- Resolved
-
-
JENKINS-25851 Richer return value for build step
-
- Resolved
-
- links to
Integration with JENKINS-27127 could mean that after spawning a build of another job, you could do other work but be asychronously notified of its completion. This would be a bit tricky it requires that there be a return value for build (
JENKINS-25851) even when in asynchronous mode; the value would have to somehow represent a Queue.Item, but be convertible to a Run if and when it is scheduled.(
JENKINS-27096at least means that we are tracking the queueId associated with a given Run, though there is currently no reverse index—meaning you would either have to search through builds of the target job for the one matching the known ID, or maintain your own QueueListener.onLeft.)