Pipeline uses 2 executors when changing node

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Pipeline uses 2 executors when changing node

Andreas Tscharner-2
Hello World,

Our setup:
* Jenkins 2.32.2 on Debian Linux
   libvirt Plugin for Jenkins
* 8 VMs on the same server, running Windows 7, building our software
   KVM/QEMU VMs, using libvirt
   labelled "build"
* 4 Ubuntu machines containing 2 VMs each (=8) running Windows 10,
testing our software
   KVM/QEMU VMs, using libvirt
   labelled "aat"

Now I created a pipeline which starts at a "build" node. It runs there
and displays "part of ...".
Now at some point in the pipeline I want to switch to an "aat" node for
testing; I use the step command "build 'SmokeTest'"). It switches to one
of the "aat" nodes (displaying "part of ...") and then the actual job
(SmokeTest) starts at a second "aat" node. The job at the first "aat"
node is just waiting.

How can I make sure that only one "aat" node is being used?

TIA and best regards
        Andreas
--
Andreas Tscharner                             <[hidden email]>
----------------------------------------------------------------------
"Intruder on level one. All Aliens please proceed to level one."
                                       -- Call in "Alien: Resurrection"

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2033b570-fe94-dd86-fd49-1a0ef13a643e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[SOLVED] Re: Pipeline uses 2 executors when changing node

Andreas Tscharner-2
On 19.05.2017 15:31, Andreas Tscharner wrote:
> Hello World,

Hello again,
>

I found the solution.
> Now I created a pipeline which starts at a "build" node. It runs there
> and displays "part of ...".
> Now at some point in the pipeline I want to switch to an "aat" node for

I switched to that aat node using "agent { label 'aat' }"; that worked,
but the job itself was also marked to work only on a node with label
aat, so I think it then switched again.
If I just skipped the "agent" statement, it worked (one job) as expected.

Best regards
        Andreas
--
Andreas Tscharner                                 [hidden email]
------------------------------------------------------------------------
Der entscheidende Vorteil eines Chats gegenueber einem normalen Telefon-
anruf ist der, dass ersterer langsamer geht und mehr kostet (fuer den
lebenswichtigen Austausch von Informationen wie "hya folks", "C U
l8er" und ":-)") ...                       Aus Murphy's Computergesetzen

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2b566496-8f81-4459-7d4c-2288abc1b0dd%40gmail.com.
For more options, visit https://groups.google.com/d/optout.