I've not found a way to define a job which will run on all build slaves and which adapts automatically to the addition and removal of slaves. My technique has been to define a multi-configuration job and individually select each node which should execute the job. Mark Waite
>________________________________ > From: Kenneth Nielsen <kenneth.f.niel...@gmail.com> >To: jenkinsci-users@googlegroups.com >Sent: Tuesday, February 5, 2013 11:57 PM >Subject: how to ensure a job executes on all slaves. > > >Hi all, > > >We have just upgraded some 3rd party libraries we use. >I would like a Jenkins job to pull them from subversion onto all our windows >build slaves. >I have them grouped under a label. > > >thanks >kenneth -- >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. > > > > > -- 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.
