-
Improvement
-
Resolution: Fixed
-
Minor
I noticed that job input parameters are not available inside of the sh task
for example:
sh 'echo ${ARTIFACTS}'
I'm aware of that I can interpolate the variable but I have scripts which expects to have variables set.
// expects to have ARTIFACTS env available sh('./some-python-script.py'))
Migration from my old hand patched pipeline to the new workflow would be easier if Job parameters and injected environment variables are available like in the regular script step (freestyle project)
- is blocking
-
JENKINS-28447 CpsScmFlowDefinition does not resolve variables
-
- Resolved
-
- is related to
-
JENKINS-29952 Allow access to environment variables as Groovy variables
-
- Resolved
-
- links to
[JENKINS-30910] Job parameters should be exposed as environment variables
Link |
New:
This issue is related to |
Summary | Original: job input parameters should be exposed in sh task | New: Job parameters should be exposed as environment variables |
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Link |
New:
This issue is blocking |
Labels | New: followup |
Epic Link | New: JENKINS-35394 [ 171187 ] |
Workflow | Original: JNJira [ 166037 ] | New: JNJira + In-Review [ 182258 ] |
Possible in conjunction with
JENKINS-29952andJENKINS-27295, I think: the current flattened parameters could be moved to environment variables, which would like all other env vars be accessible via Groovy as now, and there would be a separate pseudovariable which would give access to typed objects and more.