Hi Everyone -
I have one master and one slave node.
I am trying to move some Jenkins jobs that currently run on the master to
instead run on the slave.
For various reasons, I need (or at least want) to use the $JENKINS_HOME env
variable in my scripts, but it returns the value of the master jen
.@cisco.com > wrote:
>
>> Use the Configuration Slicing Plugin :
>> https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin to
>> mass assign a label to jobs that are not tied to any node all at once.
>>
>> -Indra
>>
>> From: > on behalf of B
lugin :
> https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin to
> mass assign a label to jobs that are not tied to any node all at once.
>
> -Indra
>
> From: > on behalf of Bruce
> Epstein >
> Reply-To: "jenkins...@googlegroups.com " <
Hi All,
Thanks to those who answered my previous question about setting up agents.
I now have two new agent nodes set up and want to move old jobs off the
master, so the master won't be used for any building (just admin).
How do I prevent jobs from running on the master? Do I just set "number o
ter, for about 60 hours a day
> and ~1000 active jobs.
> * IMO directly go to two or three agents and not just one. This way you'll
> maybe avoid (your users) designing builds to depend on a specific machine.
> ** Corollary: never use node names as labels.
>
> My 2 cents
&
Hi -
I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.)
but not an IT/administrator, and my IT dept is not that familiar with
Jenkins scaling.
If anyone can point me to a comprehensive discussion of the best way to
scale, please provide a url.
Current architecture:
O
