On Wed, May 14, 2014 at 3:28 AM, Panikera Raj <[email protected]> wrote:
>
> As you Said Master and Slave will have Same Label name, and label will
> distribute builds to which one is free, wright,
>
> But not sure why it's not able to distrubute build to slave, Always it's
> sending request to master only
>
The labels should be identical on each system - and usually something
that is related to their capabilities so they make sense as you add
more. Then use this label in the job's 'Restrict where this job can
run'. Jenkins will normally run the job on the node where it ran
last if an executor is available there, so it will continue to build
on the master unless it is busy. If the number of executors that you
have on the master are all busy, it will go to another node that
matches.
--
Les Mikesell
[email protected]
--
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/d/optout.
