I experience the same effect. 

I have a top-level agent definition for the agent I want to use by default.
In some underlying step I want to use a very specific agent, this override 
works great.
However, if I use "agent none" in an underlying step to accept input, the 
"default" node is still being used!
This is really annoying because now I have to put "agent none" at the 
top-level and a specific agent for each step.
This has the side effect that an SCM checkout is done every time.

Is there an open bug for this already?

-- 
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/e730ea42-d3b8-472e-b6cb-5204c2429362%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to