Hi Baptiste * * Thanks for responding. We're not asking about Jenkins ability to find a free slave. We're asking if what we plan to do would still work when Jenkins/Hudson sees a new slave with moved jobs from another slave previously. Is the proposed manual move, would it still work ?
Thanks * * On Monday, August 12, 2013 1:49:38 PM UTC-7, Baptiste Mathus wrote: > > Not sure I totally understand. > If what you ask is "is having two slaves instead of just one handled > correctly?" then the answer sure is yes. > > When starting jobs, jenkins master will just see which slaves have > available executor and launch builds on the free ones. > > Cheers > Le 12 août 2013 19:31, "Z W" <mpc...@gmail.com <javascript:>> a écrit : > >> Hi All >> >> We have a slave that's running out of disk space. >> To create room, we thought we like to manually move those folders under >> slave's workspace to another new slave under the new slave's workspace. >> >> Would Jenkins/Hudson still work to use both slaves when kicking off jobs ? >> >> Thanks >> Sincerely >> >> -- >> 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-use...@googlegroups.com <javascript:>. >> 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
