Could you use the capability of the Parameterized Trigger Plugin to "Restrict matrix execution to a subset"? Your original job would need to use the parameterized trigger plugin to define that the jobs which it triggered would be limited to the same slave where you ran the original job.
I haven't used the parameterized trigger plugin, so that is just me guessing, rather than an assurance it will work for your needs. Mark Waite >________________________________ > From: Thomas Sundberg <t...@kth.se> >To: jenkinsci-users@googlegroups.com >Sent: Tuesday, June 19, 2012 4:37 AM >Subject: Many jobs at the same slave > >Hi! > >I have a distributed setup with many similar slaves. I have suites of >job that I need to have executed consecutive on the same slave. Is >there any good way to make sure that all jobs end up on the same >slave? It doesn't matter which slave as long as it is the same as the >initial job was started at. > >The way I do it today is to tie all jobs in one suite to the same >slave. It works ok. But I am looking for a way to utilise the usage of >the slaves a bit more and maybe have less slaves running. > >Any suggestions? > >/Thomas > >-- >Thomas Sundberg >M. Sc. in Computer Science > >Mobile: +46 70 767 33 15 >Blog: http://thomassundberg.wordpress.com/ >Twitter: @thomassundberg > >Better software through faster feedback > > >
