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

Allow expansion of environment variables in the configuration

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • deploy-plugin
    • None

      Ahoy,

      I'm creating a deployment build that's parameterized with a "Choice" pull down list. The goal is to deploy the war to the IP address specified by the build parameter. Currently the form fields do not resolve environment variables so the IP Address is never expanded to the selected value.

      I've tested this with a Tomcat 7 deploy and eyeballed the code and I don't see any resolving for any of the Tomcat Deployment Containers.

      I think this would be nice.

      Thanks,
      Brian

          [JENKINS-12825] Allow expansion of environment variables in the configuration

          Zachary Young added a comment -

          I would like to see this also, with variable expansion in the list of WAR/EAR files to be deployed such that it handles a list like 'foo.war, , baz.war' correctly (the list in the configuration being '$deploy_foo, $deploy_bar, $deploy_baz', and the user chose to leave the '$deploy_bar' variable empty to omit it from the deployment).

          Zachary Young added a comment - I would like to see this also, with variable expansion in the list of WAR/EAR files to be deployed such that it handles a list like 'foo.war, , baz.war' correctly (the list in the configuration being '$deploy_foo, $deploy_bar, $deploy_baz', and the user chose to leave the '$deploy_bar' variable empty to omit it from the deployment).

          Rainer Weinhold added a comment -

          +1 Would love to have this.

          Rainer Weinhold added a comment - +1 Would love to have this.

          Ryan Walls added a comment -

          +1 - would help a lot when deploying to multiple environments.

          Ryan Walls added a comment - +1 - would help a lot when deploying to multiple environments.

          Wojciech Trocki added a comment -

          If anyone interested: It's fixed on my fork:
          https://github.com/fexcowtr/deploy-plugin

          Wojciech Trocki added a comment - If anyone interested: It's fixed on my fork: https://github.com/fexcowtr/deploy-plugin

          mturra added a comment -

          Why use a fork instead of improve the existing?

          mturra added a comment - Why use a fork instead of improve the existing?

          Robin Jansohn added a comment -

          This has been fixed in the master already and will be available with the next release v1.14 which should be out next week.

          Robin Jansohn added a comment - This has been fixed in the master already and will be available with the next release v1.14 which should be out next week.

            Unassigned Unassigned
            hand_of_henry hand_of_henry
            Votes:
            8 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: