Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
-
workflow-step-api 2.19, workflow-support 3.2, workflow-cps 2.63
Description
For monitoring purposes it can be useful to be able to have access to the current FlowNode/Step via environment variables.
This could be done by only injecting the current FlowNode id as environment variable.
A more flexible approach would be a new extension point, similar to an EnvironmentContributor, but called with the current StepContext.
If this idea gets a general go-ahead I will present a prototype.
Previous discussion: https://groups.google.com/forum/#!topic/jenkinsci-dev/VBYvIv3S_r4
shubbard Probably you are seeing that error because of Pipeline Supporting APIs 3.2 (my guess is that you are running 2.x). See the wiki page for that plugin for details about that compatibility issue. If you are running Pipeline Supporting APIs 3.x already, then please list the versions of those plugins you have installed.