-
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.
Code changed in jenkins
User: cjo9900
Path:
src/main/java/hudson/plugins/git/GitRevisionBuildParameters.java
src/main/java/hudson/plugins/git/RevisionParameterAction.java
src/main/resources/hudson/plugins/git/GitRevisionBuildParameters/config.jelly
src/main/resources/hudson/plugins/git/GitRevisionBuildParameters/help-combineQueuedCommits.html
src/test/java/hudson/plugins/git/RevisionParameterActionTest.java
http://jenkins-ci.org/commit/git-plugin/e442a7904904256ff9aa79e885c085cacd514ede
Log:
JENKINS-15160add support for combining git hashs when passed downstreamDon't combine with manually started builds