On Wed, Apr 24, 2013 at 10:50 AM, Les Mikesell <lesmikes...@gmail.com> wrote: >>> >> Alright. So there just is no way to have a multi configuration job reuse the >> same checkout? > > No, in the general case, the jobs will run on different slaves and may > be checked out with different native line endings. And they may run > in parallel so they can't use the same workspace. If you are really > just doing everything in one build on one host, why not write your own > script wrapper to handle the variations? >
On a second thought - maybe you could make it work with "Use custom workspace" and "." for the "directory for sub-builds" (see https://issues.jenkins-ci.org/browse/JENKINS-8317). But you may need to think about the checkout strategy (probably revert before update) and use the 'run each configuration sequentially' option. -- 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.
