I´m sorry. It was important to set the node-name in the "restrict where job
can run"
No it works like a charm :) jenkins is now deploying the project on the
right nodes
Mnnny thanks!!!
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
On Thu, Jan 9, 2014 at 5:39 PM, Paul McGregory wrote:
> Tried both options "restrict where job can run" on/off (but without label)
What do you mean 'without label'? I always assign labels to the nodes
and restrict jobs by label so I can have pools for similar jobs, but
it should work with node n
Tried both options "restrict where job can run" on/off (but without label)
This are the first logs
> Build on Slave Server3 in workspace /var/www/project-213-3.5.2
> FATAL: Failed to mkdirs: /var/www/project-213-3.5.2
>
>
It failes, because /var/www does not exist on Server3 and this should be
On Thu, Jan 9, 2014 at 11:40 AM, Paul McGregory wrote:
> I am using the custom workspace parameter (
> /var/www/project-${BUILD_NUMBER}-$tag ) and node-names
>
> He is build the job on the wrong node with the workspace parameter from the
> correct job.
I don't understand how a custom workspace wo
I am using the custom workspace parameter (
/var/www/project-${BUILD_NUMBER}-$tag ) and node-names
He is build the job on the wrong node with the workspace parameter from the
correct job.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To u
On Thu, Jan 9, 2014 at 5:36 AM, Paul McGregory wrote:
> Hey,
>
> I have 5 differend Slaves for different projects.
>
> Sometimes jenkins is deploying a job to a wrong slave, sometimes on the
> master. The executor is set by 0 on the master, the nodes by a value of 1
> I find out, that if i set all
Found exactly the same in my jenkins log file:
https://issues.jenkins-ci.org/browse/JENKINS-20769
--
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 jenkinsci-
Hey,
I have 5 differend Slaves for different projects.
Sometimes jenkins is deploying a job to a wrong slave, sometimes on the
master. The executor is set by 0 on the master, the nodes by a value of 1
I find out, that if i set all slave by "deploy on demand", jenkins is alway
just deploying on
