-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.89.4
The input step in declarative pipeline (JENKINS-48379) cannot access the environment blocks. Thus, dynamic data (e.g. version number) cannot be used in the input dialog. Also defining options in the input and checking the result requires redundant values, because they cannot be reused.
- Access to $JOB_NAME and ${env.JOB_NAME} is working.
- Access to $myVar is not working. It leads to a "no such property" exception. It doesn't matter if the variable is declared in the global or stage-local environment block.
- Access to ${env.myVar} is not working. The value is null. It doesn't matter if the variable is declared in the global or stage-local environment block.
- relates to
-
JENKINS-48379 Input/parameters for Stages
-
- Closed
-
Part of this another ordering issue, like
JENKINS-49947: either we can have input results available when evaluating its stage's environment or the other way around, but not both. But top-level environment variables should be available to input - that's a bug. Can you provide a simple Jenkinsfile reproducing this? Thanks!