On Fri, Sep 6, 2013 at 12:32 PM, James Nord (jnord) <[email protected]> wrote: > Hi Les, > > I don't think there is a way to get the svn to checkout the same revision > (however I may be wrong.) > But you can have one build checkout the code - and then archive that builds > workspace "as an SCM", and then get your other jobs to checkout from that > build.
The parent job is polling svn - if there is a way to get the revision number that triggered the build, it should be possible to paramaterize the child jobs to expand @rev_number at the end of the svn repository path. I'd think this part would be a common problem for any multi-step job. > (ie have a job that only does a checkout) > https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin > > As for collating the artifacts - you could probably do that as a build flow > extenstion if you feel like writing some code. I was hoping to use one of the existing plugins for that - maybe 'Copy To Slave' if I can get the parent to save the child build numbers so it can get the right ones. -- Les Mikesell [email protected] -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
