On Mon, Jun 4, 2012 at 9:13 AM, Bram de Jong <bram.dej...@samplesumo.com> wrote: > On Mon, Jun 4, 2012 at 5:27 PM, Bram de Jong <bram.dej...@samplesumo.com> > wrote: >>>> My initial guess on how to solve this: >>>> * put each of the repo's in a job that *only fetches* the repo into a >>>> shared directory and doesn't do anything else. >>> >>> I'd think in terms of jobs that build components and applications, not >>> so much in relationships to repositories. >> >> The problem is that this would mean 100 different jobs that all do the >> same thing (i.e. update 5 repositories - one of which is SUPER slow). >> Each job will have need approx 10GB of HD space to just have the >> repositories. >> I.e. the overhead of having each of the 5 repos reproduced for each of >> the 100+ jobs would be immense. > <snip> > > I suppose the gist of my question is: > If I have 50 different applications that are all sitting in the same > repository, and I want each of these applications to build separately > as a job, do I really need to do 50 different checkouts of the the > repository? > > cheers, > > - bram
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. -- Website: http://earl-of-code.com
