Details
-
Patch
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
-
workflow-support 2.23
Description
I found the description of RunWrapper.getBuildVariables a bit incomplete/confusing:
> buildVariables
>
> for a non-Pipeline downstream build, offers access to a map of defined build variables; for a Pipeline downstream build, any variables set globally on env
so I suggest changing it, appending:
> Child Pipeline jobs can use this to report additional information to the parent job by setting variables in <code>env</code>. Note that build parameters are not shown in buildVariables.
Attachments
Issue Links
- links to
Activity
Craig Ringer
created issue -
Craig Ringer
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
I found the description of RunWrapper.getBuildVariables a bit incomplete/confusing: > buildVariables > > for a non-Pipeline downstream build, offers access to a map of defined build variables; for a >Pipeline downstream build, any variables set globally on env so I suggest changing it, appending: > Child jobs can use this to report additional information to the parent job by setting environment variables. Build parameters are not shown in buildVariables. |
I found the description of RunWrapper.getBuildVariables a bit incomplete/confusing: > buildVariables > > for a non-Pipeline downstream build, offers access to a map of defined build variables; for a Pipeline downstream build, any variables set globally on env so I suggest changing it, appending: > Child Pipeline jobs can use this to report additional information to the parent job by setting variables in <code>env</code>. Note that build parameters are not shown in buildVariables. |
Craig Ringer
made changes -
| Remote Link | This issue links to "workflow-support-plugin/pull/80 (Web Link)" [ 22017 ] |
| Released As | workflow-support 2.23 | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |