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.

          [JENKINS-49946] input step cannot access environment blocks

          Andreas Klemp created issue -
          Andreas Klemp made changes -
          Link New: This issue relates to JENKINS-48379 [ JENKINS-48379 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-model-definition-plugin [ 21706 ]
          Component/s Original: pipeline [ 21692 ]
          Andrew Bayer made changes -
          Assignee New: Andrew Bayer [ abayer ]
          Andrew Bayer made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          ipleten made changes -
          Assignee Original: Andrew Bayer [ abayer ] New: ipleten [ tamerlaha ]
          Erik Nummela made changes -
          Assignee Original: ipleten [ tamerlaha ] New: Andrew Bayer [ abayer ]
          Erik Nummela made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]

            Unassigned Unassigned
            aklemp Andreas Klemp
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: