Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28764

Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • active-choices-plugin
    • None
    • Version 1.0 of Active Choices plugin

      I'm using a "Active Choices Parameter" on a parameterized build (by selecting "This build is parameterized" in the job settings). If I've defined a global environment variables/properties or password in Jenkins (defined under "Manage Jenkins" -> "Configure System" -> "Global Properties" and "Manage Jenkins" -> "Configure System" -> "Global Passwords") I cannot seem to use these (for example ${MY_ENV_NAME}) as an input parameter to Scriptler scripts. This means that I have to duplicate my global environment variable value when used together with the active choice plugin which is not optimal. The passwords are also visible in clear text when configuring the project.

            kinow Bruno P. Kinoshita
            johanhaleby Johan Haleby
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: