Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-75109

Consecutive Trigger/call builds on other projects trigger single build

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Jenkins Version 2.483, parameterized-trigger plugin version 806.vf6fff3e28c3e, Kubernetes plugin 4295.v7fa_01b_309c95, Java version 17.0.13.

      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.

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

          Markus Winter added a comment -

          If the triggered job is still in the queue and the parameters are identical then this behavior is expected for freestyle jobs. That should not happen for pipeline jobs as they start immediately

          Markus Winter added a comment - If the triggered job is still in the queue and the parameters are identical then this behavior is expected for freestyle jobs. That should not happen for pipeline jobs as they start immediately

            Unassigned Unassigned
            georges474 Georges Zwingelstein
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: