If you don't restrict the job, it will pick one of the available nodes
arbitrarily, and it doesn't matter whether it is the master or a
slave/agent. Once the job has run on a particular node, it will remain
there unless that node is unavailable at the time the job starts. This
is done to take advantage of any dependencies or resources that may
already be there from a previous run.
Generally, it is considered better to have jobs run on agents, and let
the master node just run Jenkins.
Regards,
Eric
On 12/17/2018 3:54 AM, [email protected] wrote:
I have a job it's doesn't use "Restrict where this project can be run"
option, why doesn't it running on a master node, but running on a
slave node?
Jenkins ver. 1.625.1
Could you help me to know?
--
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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1078c386-120f-40cc-b758-adbf1aa925aa%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/1078c386-120f-40cc-b758-adbf1aa925aa%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Eric Pyle
Siemens PLM Software
Lebanon, NH
+1 603-277-3060
[email protected]
http://www.siemens.com/plm
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1b6a88fd-ba0d-23f0-a2d9-1c7833cb478d%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
