-
Bug
-
Resolution: Fixed
-
Major
-
None
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.
[JENKINS-15160] earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times
Assignee | Original: huybrechts [ huybrechts ] | New: cjo9900 [ cjo9900 ] |
Component/s | New: git [ 15543 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 145881 ] | New: JNJira + In-Review [ 191673 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |