This may be something that I've missed but how are you planing on adding support to add build wrappers to the Workflow plugin. We depend a lot on a few plugins to modify the console output to for example color code, find match patterns and to filter out password.
- depends on
-
JENKINS-26552 @StepContextParameter EnvVars missing Computer.environment
-
- Resolved
-
-
JENKINS-28719 Store environment variable values for CoreWrapperStep as Secret
-
- Open
-
-
JENKINS-27392 API to decorate console output
-
- Resolved
-
- is blocking
-
JENKINS-26051 Workflow integration for Credentials Binding
-
- Resolved
-
-
JENKINS-27207 Add timestamps to workflow console output
-
- Resolved
-
-
JENKINS-27413 Handle file parameters
-
- Resolved
-
-
JENKINS-28689 Make SSH Agent Plugin compatible with Workflow
-
- Resolved
-
-
JENKINS-26477 XVNC integration with Workflow
-
- Resolved
-
-
JENKINS-27098 Support outputting deployments to environment-dashboard
-
- Resolved
-
-
JENKINS-26339 Workflow integration for Config File Provider
-
- Closed
-
-
JENKINS-26953 Workflow support for Build User Vars
-
- Closed
-
- links to
Build wrappers could perhaps be integrated by defining a SimpleBuildWrapper API (analogous to SimpleBuildStep and so taking Run and FilePath rather than AbstractBuild) where Environment is considered Serializable, and introducing a generic Step to run these. This could make it easier to use xvnc-plugin etc.
The tool-env plugin does not need this, due to the standard tool step.