[JENKINS-46682] Downstream jobs not always triggered by "build" pipeline step

We have several jobs set up to trigger other downstream builds. One of our main job is written to kick off 6 downstream jobs using the 'build job' Jenkinsfile pipeline script code.

However, the downstream jobs are only automatically built some of the times, not all.

And sometimes when some of the downstream jobs are started, the rest aren't.

I've looked in the main Jenkins log file, and there is (unfortunately) no logging which appears around the time that either the upstream job started/stopped or when the downstream job should have been started relating to this. I would greatly appreciate any tips to maybe add additional logging, or where else to look for logging regarding this particular build step.

We're running Jenkins 2.60.3.

Upstream job relevant code:

stage("Build dependencies if branch is develop") {

if( newBranch.matches('develop')) {

build job: 'job1', wait: false

build job: 'job2', wait: false

build job: 'job3', wait: false

build job: 'job4', wait: false

build job: 'job5', wait: false

build job: 'job6', wait: false

}

}

 

I do apologize for the lack of detailed information, however there doesn't appear much that I can provide from our Jenkins server.

---
Originally reported by srepetsk, imported from: Downstream jobs not always triggered by "build" pipeline step

• status: Open
  
• priority: Minor
  
• component(s): pipeline
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-08
  

Raw content of original issue

We have several jobs set up to trigger other downstream builds. One of our main job is written to kick off 6 downstream jobs using the 'build job' Jenkinsfile pipeline script code.


However, the downstream jobs are only automatically built some of the times, not all.


And sometimes when some of the downstream jobs are started, the rest aren't.


I've looked in the main Jenkins log file, and there is (unfortunately) no logging which appears around the time that either the upstream job started/stopped or when the downstream job should have been started relating to this. I would greatly appreciate any tips to maybe add additional logging, or where else to look for logging regarding this particular build step.


We're running Jenkins 2.60.3.


Upstream job relevant code:


stage("Build dependencies if branch is develop") {

 if( newBranch.matches('develop')) {

 build job: 'job1', wait: false

 build job: 'job2', wait: false

 build job: 'job3', wait: false

 build job: 'job4', wait: false

 build job: 'job5', wait: false

 build job: 'job6', wait: false

 }

 }


 


I do apologize for the lack of detailed information, however there doesn't appear much that I can provide from our Jenkins server.

Start with the Jenkinsfile snippet in the issue and reproduce the develop-branch stage using Jenkins 2.60.3, watching whether all six `build job` steps run with `wait: false`. Inspect the available upstream and downstream build logs for the point where triggering stops. Done means the cause is identified and all six downstream jobs trigger consistently, with useful logging if a trigger fails.

Written by the indexing model from the issue text.