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. (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. /James > -----Original Message----- > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci- > us...@googlegroups.com] On Behalf Of Les Mikesell > Sent: 06 September 2013 17:21 > To: jenkinsci-users > Subject: build flow job artifacts > > I'd like to use the build flow plugin as an alternative to a matrix build to > run > approximately the same job on different platforms but with a bit more > control. But, is there any way to (a) ensure that the jobs it triggers all > build > from the same (subversion) revision that triggered the parent, and (b) to > collate all of the artifacts under the parent job? > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
