-
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
