Discussing an interesting scenario with my tech lead at work today. Might try this out but was looking for any definitive remarks indicating we may be trying to divide by zero.
We need to build up a few slaves since our single instance is becoming overwhelmed. The thought was that since this is entirely local network-wise that we possibly try this: Master system with all jobs and workspaces in directory X. Slaves setup to mount X as CIFS to run their jobs on. We need the horsepower, not the space, so we're trying not to waste it, hence the CIFS idea (which could add to build time, which could be acceptable). So I'm wondering... is that too far off the rails? Would we need to segregate jobs to run only on certain slaves? Does the shared mount bring along issues of configurations being overwritten or not read properly by each Jenkins instance? Thanks for pondering. -- 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.
