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
Attachments
Issue Links
Activity
Thomas Weißschuh
created issue -
| Field | Original Value | New Value |
|---|---|---|
| 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. Cc [~svanoort], [~abayer] Previous discussion: https://groups.google.com/forum/#!topic/jenkinsci-dev/VBYvIv3S_r4 |
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. Cc [~svanoort], [~abayer] Previous discussion: https://groups.google.com/forum/#!topic/jenkinsci-dev/VBYvIv3S_r4 |
Thomas Weißschuh
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Thomas Weißschuh
made changes -
| Assignee | Sam Van Oort [ svanoort ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
| Remote Link | This issue links to "jenkinsci/workflow-step-api-plugin#36 (Web Link)" [ 22337 ] |
| Remote Link | This issue links to "jenkinsci/workflow-support-plugin#62 (Web Link)" [ 22338 ] |
| Remote Link | This issue links to "jenkinsci/workflow-step-api-plugin#36 (Web Link)" [ 22339 ] |
| Remote Link | This issue links to "jenkinsci/workflow-cps-plugin#229 (Web Link)" [ 22340 ] |
| Remote Link | This issue links to "jenkinsci/workflow-step-api-plugin#36 (Web Link)" [ 22337 ] |
| Released As | workflow-step-api 2.19, workflow-support 3.2, workflow-cps 2.63 | |
| Assignee | Sam Van Oort [ svanoort ] | Thomas Weißschuh [ t8ch ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Resolved [ 5 ] |