-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 1.480.2
parameterized-trigger: 2.16
Child builds of matrix jobs should use the same subversion revision as the parent job to ensure consistent builds across axes.
An example of where this doesn't happen: I use the parameterized-trigger plugin to pass the subversion revision from an upstream build job to a downstream matrix job.
While the parent matrix build correctly picks the revision, the child builds just use the HEAD revision instea,
- is related to
-
JENKINS-14619 SVN revision in Matrix Project problem triggered by Parameterized Build
-
- Closed
-
Might be related to
JENKINS-14619And issue may occur where the Revision action is created in the parent but when passed to child jobs there have been additional commits during the checkout/update of the parent.