I don't want the master to do anything. I want all the slaves to do the job. If that's something that is done by design I'll be happy to read the documentation (in case it exists). And for starters I don't know what the * name* and the *values* of the user axes should be and more important - *why*should they be the ones that Bertrand specified.
On Wednesday, April 24, 2013 4:06:13 PM UTC+3, Stephen Connolly wrote: > > Did you wait for the master to finish checking out the source code and > then start replicating the workspace to all slave nodes? > > > On 24 April 2013 13:57, Ceco <[email protected] <javascript:>> wrote: > >> Thank you for your answer. I guess you misjudged my knowledge about >> Jenkins though and therefore there's no progress. >> >> 1. After searching a lot I figured out I have to use master and slave >> nodes which I believe I've set up correctly in a way that works for me. >> 2. I created the two axes with the specified values. But when I build the >> job only the master node is building, not the slave nodes. I want it to be >> the other way around - the master should not be running the job, each slave >> should do that. If only there was a way to find out what the values should >> be in order to force the job to be run by the slave nodes. I find the lack >> of documentation about this project extremely frustrating. >> >> -- >> 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] <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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
