On Thursday, February 26, 2015 at 1:13:00 PM UTC-5, Timothy Wojtaszek wrote: > > this means that for a node block, the master executing the workflow is > effectively communicating with the slave for each command. >
Correct, each `sh` step, etc. means a transaction starts over the remoting channel to the slave. > the node block simply sets the context such as machine, cwd, etc. > Specifically it waits in the queue (just like a top-level job) for an available slave; allocates an executor slot when it is scheduled; locks a workspace; sets the CWD and relevant environment variables; then runs its body with that context. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0cd59665-642e-467c-9359-4edbc990a97c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
