On Tue, Jun 21, 2016 at 3:20 PM, James Read <xconspiris...@gmail.com> wrote:
> It seems that actually the Pipeline makes the whole Jenkinsfile 1x logical
> job, and the node{} blocks just allow different node selections during that
> job.
Not. Every `node` call has its workspace (and it can be erased at any time
by Jenkins core, so you never know if the workspace contains what you
think). Which means that the Jenkinsfile has to be idempotent and don't
rely on workspace contents from previous builds. Actually every node block
should remove/put whatever it needs (you can move things from one node to
another by using `stash`).
If you request for two nodes in the same Jenkinsfile using different
labels, you would be using two nodes with two separated workspaces (even in
different physical machines!).
--
Antonio Muñiz
Software Engineer
CloudBees, Inc.
--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAJc7kzRbz79%3DPmVpT4n0G1CLVnd4fhNA56FYBLkhy_4mupw3gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
