![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
matrix, subversion |
|
Created:
|
11/Feb/13 11:38 AM
|
|
Description:
|
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,
|
|
Environment:
|
Jenkins 1.480.2
parameterized-trigger: 2.16
|
|
Project:
|
Jenkins
|
|
Labels:
|
jenkins
subversion
matrix
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Chris Withers
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
