wrong workspace picked up by node(..) when running parallel jobs

[Torsten Reinhard]

Hi, 

this pipeline sample fails, when started multiple times and running in 
parallel at the same time.
Assigning a captured node again seems to be not enough - the workspace 
isn´t matching than what will lead to very strange behaviour.

import com.cloudbees.groovy.cps.NonCPS

String buildNode
String buildNodeWS

@NonCPS 
assertWorkspaces(current, expected ) {
    assert current == expected
}

node() {
    buildNode = env.NODE_NAME
    buildNodeWS = env.WORKSPACE
    echo "performing build on node ${buildNode} in ${buildNodeWS}"
}

checkpoint("built")
node('sdp') { 
    echo "running on any node, currently it´s ${env.NODE_NAME}"
}
checkpoint("deployed")

node( buildNode ) {
    String currentWS = env.WORKSPACE
    echo "running on ${buildNode} again - it´s ${env.NODE_NAME} in 
${currentWS}"
    
    assertWorkspaces(currentWS, buildNodeWS)
}

Do I have to manage the workspace by myself - or is that a bug to be 
reported?

What do you think ?

Torsten

-- 
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/de418afb-05cd-4d96-bfdb-cf7cee9f4f9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.