Yes, this should work just fine. There is a page on the wiki that talks about using a system as a slave for two Jenkins' instances, using it for the way you describe would probably be similar. You would definitely have to have different directories for each CI server on the slave. You can see [1] for info on using a computer with multiple masters.
slide 1 - https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-RunningMultipleSlavesontheSameMachine On Mon, Feb 17, 2014 at 1:35 PM, mpc8250 <mpc8...@gmail.com> wrote: > Hi > > Can we have a slave configured such that it serves both Hudson and Jenkins > ? > We would have different directories for each CI server on the slave ? > Is there any port number conflict we should be worried about when using > this configuration setup ? > > Thanks > > -- > 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. > -- Website: http://earl-of-code.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.
