Sounds like a bug into declarative pipeline and the agent. I'm no declarative
pipeline, so you may want to check the agent doc to know if the position is
correct into the script.
> On May 9, 2017, at 7:00 PM, SamL wrote:
>
> The label Axis is not in the Master
>
> At the moment I have the Ma
The label Axis is not in the Master
At the moment I have the Master and one agent
The Master has the label 'Master' and Only build jobs with label
expressions matching this nose
The Agent has the label 'Axis' and Use this node as much as possible
On Tuesday, May 9, 2017 at 12:28:25 PM UTC-
One more thing when I look at the log output it says that it is running on
the slave with the specified label. Yet the SCM step gets executed on the
Master
On Tuesday, May 9, 2017 at 12:21:21 PM UTC-7, SamL wrote:
>
> Thank you very much for the reply
>
> The slave has the Label Axis on its co
Because if both master and slave have the Axis labels and both are setup to
be used, there's multiples option to build, the first free may be taken (in
your case probably the master is taken). Maybe there's a bug into the usage
(
'use as much as possible' and the 'only use when labels match') but a
Thank you very much for the reply
The slave has the Label Axis on its configuration.
Slave is already configured to be used as much as possible.
I have put a label on the Master and configure it so then only jobs
matching the name run in it.
But sadly the results are the same.
On Tuesday,
How is your slave labels configured?
If nothing match is found, I think the code run on the master. Also make
sure the master node doesn't have the labels Axis. You also may want to
change the usage of each node (node configuration). May want to mark your
master to be used only when matching an
Hello Folks
I have this simple Pipeline script
pipeline {
agent none
stages {
stage ('Check out the Code') {
agent { label 'Axis' }
steps {
echo 'Checking out Source from Mercurial'
checkout changelog: true, scm: [$class:
