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

earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Job A triggers job B and passes its git hash along. Job A is fast but job B is slow. So there are times when job A finishes and triggers job B while job B is still running and processing the earlier git hash. When job B finishes its current run, the next run would be triggered by multiple runs of job A. The parameterized trigger passes the git hash from the earliest trigger by job A. As a result, git hashes from the later triggers are never processed by job B. The parameterized trigger should pass the git hash from the latest trigger by job A.

        Attachments

          Activity

          hlau hlau created issue -
          cjo9900 cjo9900 made changes -
          Field Original Value New Value
          Assignee huybrechts [ huybrechts ] cjo9900 [ cjo9900 ]
          cjo9900 cjo9900 made changes -
          Component/s git [ 15543 ]
          scm_issue_link SCM/JIRA link daemon made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          inger Gergely Nagy made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          scm_issue_link SCM/JIRA link daemon made changes -
          Status Reopened [ 4 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 145881 ] JNJira + In-Review [ 191673 ]

            People

            • Assignee:
              cjo9900 cjo9900
              Reporter:
              hlau hlau
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: