What you need to do is pass the parameter for the SVN_REVISON that is
generated in the first job down to the chained jobs.
Simple solution using parameterized trigger plugin[1]
(assumes you don't want to start downstream jobs directly with parameters)
Start job, has REVISION string parameter,
This uses parameterized trigger plugin to start job 2 with the revision
actually used (SVN Revision parameter)
Assuming job 2-n all use the SVN SCM then the checkout will occur with the
same version as the start of the chain.
This means that you can remove the @{SVN_REVISION} from these jobs.
More complex solution using parameterized trigger plugin[1]
(if you want to start downstream jobs directly with parameters)
Start job, has REVISION string parameter,
This uses parameterized trigger plugin to start job 2 with the revision
actually used
pass a Predefined Parameter REVISION=$SVN_REVISION
See subversion wiki page[2] section "Subversion Revision and URL
information as Environment Variables" for the env definitions.
Assuming job 2-n all have string parameter REVISION default to HEAD
jobs 2->n-1 must also pass the same parameter downstream, but can just pass
the original parameter either Current Parameters or Predefined Parameter
with REVISION=$REVISION.
Hope this helps.
[1] https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
[2] https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin
On Wednesday, 9 January 2013 08:37:07 UTC, zw wrote:
>
> Hi All
>
> We have a chained job (4 subjobs, chained together).
> All the subjobs's Repository URL has similar strings like
> https://abcdef.wsxedc.com/svn/prod/1.0/src@${SVN_REVISION}
> We set the first chain job with This build is parameterized - String
> parameter - name as SVN_REVISION, value as <HEAD or a number>
> When we set to HEAD, we get different revision numbers.
> When we set to a number, we get the same revision number, which is good
> but when our job is scheduled, it is not picking the latest revision number
> that should be used by
> all the other jobs. Using HEAD didnt help since any future checkins during
> the run are used.
> We like all the chained job to use the same revision number in checking
> out/updating files.
> How do we set the This build is parameterized - String parameter so that
> whatever the latest revision number that is picked up by the first job,
> that all the other jobs would use the same revision number ?
>
> Sincerely
> Thanks
>
>
