Gregg, Sounds like a very bad idea to me. As I have experienced, Jenkins caches project information in memory and blindly writes out configuration information to disk for restart purposes, and typically only reads disk data in case of a Jenkins restart. So, you could very easily end up in a situation where both masters are blindly writing (and overwriting) to the same project since neither (except in case of restart) will have any idea the other is out there. There may be something in the paid Jenkins that could do this, but nothing in the no-cost version that I'm aware of.
Scott On Mon, Aug 18, 2014 at 2:30 PM, G Dameron <[email protected]> wrote: > I'm exploring strategies for two Jenkins masters to use a common set of > projects. One thought was to collect the current (local) content of the two > masters' $JENKINS_HOME/jobs directories, move them to a filer-served area > that both masters can see (read/write), and change $JENKINS_HOME/jobs from > a directory to a symbolic link pointing to the shared filer area. > > Has anyone tried this? Any horror stories to share? > > -- > 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. > -- 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.
