It works for what we need it for, which actually isn't matrix jobs. Our setup was more in an interest of saving space and not having to keep expanding VM hard disk space as jobs are added. With a much larger network location storage space we can have multiple smaller slaves to handle the job load. We also use SVN with the emulate fresh checkout option so a lot of the workspace is already there for all the slaves.
Again it works for what we need it for, it may not work for everyone else's setup necessarily. ----- Original Message ----- From: "Les Mikesell" <[email protected]> To: "jenkinsci-users" <[email protected]> Sent: Tuesday, January 7, 2014 10:04:19 AM Subject: Re: shared workspace On Tue, Jan 7, 2014 at 9:36 AM, <[email protected]> wrote: > I was able to do this by getting a network location set up and then using > symlinks on the slave machines as the workspace directory that point to that > network location. > Did it turn out to be a good idea? A matrix job is not going to protect your files from concurrent access. Normally you'd want independent checkouts of the source and 'archive artifcacts' to consolidate the results back on the master. -- Les Mikesell [email protected] -- 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/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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
