[JENKINS-75109] Consecutive Trigger/call builds on other projects trigger single build

When a job triggers another job using the Parametrized Trigger plugin, and the other job is configured with "(v) Execute concurrent builds if necessary", "(v) Restrict where this project can be run" and "Label Expression" set to a label for agent running in a pod in a Kubernetes cluster using the plugin Kubernetes plugin for Jenkins, the triggered job will be triggered only once if triggered twice or more within 8 seconds or less.

The triggered job will show in the console output more than one "Started by upstream project "" build number ", eg:

```
Started by upstream project "trigger" build number 59
originally caused by:
Started by upstream project "test" build number 9
originally caused by:
Started by user
Started by upstream project "trigger" build number 60
originally caused by:
Started by upstream project "test" build number 9
originally caused by:
Started by user

```

Not sure if it happens with non-dynamically provisioned agents. May happen only when an agent in a Kubernetes pod needs to be allocated for the first trigger and the agent hasn't been allocated yet when the second trigger happens.

---
Originally reported by georges474, imported from: Consecutive Trigger/call builds on other projects trigger single build

• status: Open
  
• priority: Major
  
• component(s): parameterized-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-07
  

Raw content of original issue

When a job triggers another job using the Parametrized Trigger plugin, and the other job is configured with "(v) Execute concurrent builds if necessary", "(v) Restrict where this project can be run" and "Label Expression" set to a label for agent running in a pod in a Kubernetes cluster using the plugin Kubernetes plugin for Jenkins, the triggered job will be triggered only once if triggered twice or more within 8 seconds or less.


The triggered job will show in the console output more than one "Started by upstream project "<projectName>" build number <buildNumber>", eg:



Started by upstream project "trigger" build number 59

originally caused by:

Started by upstream project "test" build number 9

originally caused by:

Started by user <userName>

Started by upstream project "trigger" build number 60

originally caused by:

Started by upstream project "test" build number 9

originally caused by:

Started by user <userName>





Not sure if it happens with non-dynamically provisioned agents. May happen only when an agent in a Kubernetes pod needs to be allocated for the first trigger and the agent hasn't been allocated yet when the second trigger happens.

• environment: Jenkins Version 2.483, parameterized-trigger plugin version 806.vf6fff3e28c3e, Kubernetes plugin 4295.v7fa_01b_309c95, Java version 17.0.13.