On Mon, Jun 4, 2012 at 9:22 AM, Bram de Jong <bram.dej...@samplesumo.com> wrote: > On Mon, Jun 4, 2012 at 6:16 PM, Slide <slide.o....@gmail.com> wrote: >> No, we have a similar situation. I have a job that does the checkout >> and then set the workspace for each of the other jobs to the place >> where the SCM job checked the code out to and do the actual builds. > > Aha, and could you perhaps give me an idea of how you set this up precisely? > > > - bram > > -- > Bram de Jong - CTO > SampleSumo BVBA, Wiedauwkaai 23 G, B-9000 Ghent, Belgium > Web: http://www.samplesumo.com > Twitter: http://twitter.com/SampleSumo > Facebook: http://facebook.com/SampleSumo > Phone: +32 9 3355925 - Mobile: +32 484 154730
We only have one SCM to deal with (ClearCase) so it will be slightly different, but you may want to look into the multi-SCM plugin which may allow polling of multiple SCMs (but I digress). The way I have things setup is I have a job that polls my Clearcase for changes, when it finds changes, it updates the local working copy in a specific directory. Then it kicks off other jobs that are the actual other builds. These jobs use a custom workspace that is the directory that was updated in the upstream job. The tricky part is when you want to do distributed builds, you either have to copy the source to the slaves (which is what I do) or use a network share for the source code. Let me know if that helps, or if you need some more information. Thanks, slide -- Website: http://earl-of-code.com