For prosperity, my finding is:
1. it seem like the node have their node name as label automatically (I
realized this when trying to add the node name to the label, the label was
disappearing when saving the changes)
2. Knowning number 1 point, I could just use the named parametrized
input and ask for the node name as unique label, which was forcing the
Jenkinsfile to run on that node.
3. parametrized build is node type: name: ENFORCED_NODE, fill the rest
as wanted
4. Use it as follow into the scripted pipeline Jenkinsfiles:
println("Enforced node: $ENFORCED_NODE")
node(!ENFORCED_NODE ? 'windows && x64' : ENFORCED_NODE)
{
...
}
--
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/f39b4b3d-bf6a-4e2f-9498-9b98dd44bcae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
