|
||||||||
|
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.
@Greg Hansen
Out of the box you can use the Parameterized Trigger Plugin to pass an SVN revision number from one job to the next. The specifics on how this works aren't clearly stated on the plugin wiki unfortunately, and this configuration does have a few limitations - most notably, that all of your job configurations must share the same source / SVN URL. If this is a non issue for you then you may want to start there.
Otherwise, one thing you could try is define a custom property (ie: using the Parameterized Build Plugin) which will contain the SVN revision number, and then reference the property in your SVN configuration area in your job, something like "http://path_to_repo/project@${MY_NEW_PROPERTY}". This should force subsequent checkout operations to always check out using the given revision. You can also leverage the parameterized trigger plugin to pass revisions between projects in this way as well.