We have a bunch of matrix (multi-configuration) build jobs which are configured to use a Git plugin to pull source code into the job workspace. Unfortunately, what happens is that the parent job pulls the full set of code and expands it into the parent workspace, only to then fire off all of the child configuration jobs and redo all of the source code pulling from Git and populating for the actual builds against the configured targets into each of the child job workspaces.
Is there a reason that the parent does the pull for no apparent reason, since the parent doesn't actually do anything other than just fire off the children and wait for them to be done? If there is no reason, is there any way to disable this functionality on the parent build? We have some builds which are pulling down 8-10 gig of content for a build, and if there is a way to turn that off for the parent, we'd be far ahead with build speed performance and disk space. In our environment, the parent build could run on any number of different nodes and there isn't a built-in way to clean up those old workspaces so we are ending up with several stale parent instances as time goes on. Thanks in advance! Scott -- 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/d/optout.
