-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: pipeline-model-definition-plugin
having agent at the global level is nice, but it has come up a few times in conversations that having agents on a per-stage level is worth considering.
This makes the "blocking for input" case a lot nicer and less wasteful (without the user needing to learn additional node syntax).
CC jamesdumay hrmpw
- is duplicated by
-
JENKINS-37779 Pipeline Config: Add support for overriding "agent" per-stage
-
- Closed
-
- relates to
-
JENKINS-33510 dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
-
- Resolved
-
- links to
