-
Task
-
Resolution: Unresolved
-
Minor
-
None
for JENKINS-48050 we expect to offer an alternate implementation for "docker" agent type. This implementation should be triggered by a high level option set for the whole pipeline.
A generic mechanism to support such a global implementation switch would offer opportunities to do the same in another context
I expected we could switch to a complete distinct implementation for "agent:docker" implementation but would require SymbolLookup#findDescriptor to return a list of candidates, not just a single matching instance, then check which one offer best match for configured options. abayer do you think it would make sense to follow up in this direction and prepare a PR for structs-plugin ?