![]() |
|
|
Issue Type:
|
Bug
|
Assignee:
|
huybrechts
|
Components:
|
parameterized-trigger |
Created:
|
31/Jan/14 4:09 AM
|
Description:
|
This is our rough configuration:
Project U (upstream):
- Is a matrix project
- Runs on multiple platforms to create released files for each platform.
These put the subversion revision number inside various files.
- Archives artifacts back to Jenkins
- Triggers parameterised build on D, passing only the Subversion revision
Project D (downstream):
- Is not a matrix project
- Checks out a small subset of the code as required to do its work.
- Uses the subversion revision number to decide where to copy the merged results.
I'm finding that despite setting up the parameterised trigger, the Subversion revision it's checking out does not match.
Logs from U show it checking out revision 32983:
Logs from D show it checking out a mix of revisions, which is what you normally get if you're checking out bits and pieces of the repository:
It looks like the top-level directory revision matches revision numbers, but the directories further in do not. The timestamps do not match at any point, either.
I would expect all the revision numbers and timestamps of revisions to match between the two builds.
|
Project:
|
Jenkins
|
Priority:
|
Major
|
Reporter:
|
trejkaz
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.