(replies inline)
On Thu, 25 Feb 2016, Alex Domoradov wrote:
> Some time ago Jenkins has started run jobs on slave node (win 7).
You have a couple options to consider. One when configuring build nodes,
choosing "Only build jobs with label restrictions matching this node" will
ensure that only
Thanks, will bear in mind
On Thursday, February 25, 2016 at 3:19:17 PM UTC+2, Victor Martinez wrote:
>
> I don't know now how that version of Jenkins used to distribute the load
> and the default node setup. AFAIK, if that jenkins infrastructure is based
> on one master then those jobs will be
I don't know now how that version of Jenkins used to distribute the load
and the default node setup. AFAIK, if that jenkins infrastructure is based
on one master then those jobs will be always triggered by those 'master
slave', otherwise those jobs will require where to run.
Jenkins tries to
So, every time when I'll create a new job I must specify a node? Have I
correctly understood?
It's a little bit strange, because we have another instance with Jenkins
(ver. 1.565.2) and there all jobs by default executes on MASTER node. If I
need a job will execute on some specific node then
Hi,
You might need to configure your jobs in order to use the 'master' label,
it's part of the 'Restrict where this project can be run' configuration.
Although using your master for building and so on it's ideal.
Cheers
On Thursday, 25 February 2016 09:30:07 UTC, Alex Domoradov wrote:
>
>
Hello,
Some time ago Jenkins has started run jobs on slave node (win 7).
[EnvInject] - Loading node environment variables.
Installing JDK jdk-8u74-oth-JPR
Downloading JDK from
http://download.oracle.com/otn-pub/java/jdk/8u74-b02/jdk-8u74-windows-x64.exe
Downloading 196405336 bytes
