-
New Feature
-
Resolution: Fixed
-
Major
People often confuse Groovy variables with environment variables and do not grasp how to access the latter from outside a forked process.
CpsScript.getProperty ought to fall back to EnvActionImpl.getProperty as a convenience, so that you can access environment variables from a script as PROP_NAME in addition to env.PROP_NAME.
- is related to
-
JENKINS-29951 Supported way to get all defined environment variables
-
- Open
-
-
JENKINS-27295 Boolean parameters injected as String
-
- Resolved
-
-
JENKINS-30910 Job parameters should be exposed as environment variables
-
- Resolved
-
- relates to
-
JENKINS-33353 Document existence of steps global variable
-
- Open
-
- links to
[JENKINS-29952] Allow access to environment variables as Groovy variables
Link | New: This issue is related to JENKINS-29951 [ JENKINS-29951 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Labels | Original: envinronment-variables | New: envinronment-variables followup |
Epic Link | New: JENKINS-35394 [ 171187 ] |
Workflow | Original: JNJira [ 165030 ] | New: JNJira + In-Review [ 181797 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Component/s | New: workflow-cps-plugin [ 21713 ] | |
Component/s | Original: pipeline [ 21692 ] |