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

'Build Parameters' column displays uresolved environment variable

      We are using environment variables (Jenkins->configuration->Global properties-->Environment variables) as default values of build parameters to our Jenkins deploy application builds:
      APPLICATION_DEPLOY_VERSION=x.y.z

      Somehow there is a requirement to indicate the latest deployed application version, per application deploy job. Introducing a 'Build parameters' column in the Jenkins view seems to fulfill this requirement. This works fine if the user overrides the default value of the version build parameter (${APPLICATION_DEPLOY_VERSION}).

      But if the user accepts the default value (${APPLICATION_DEPLOY_VERSION}), the 'Build parameters' column indicates that the latest build was invoked with the parameter value '${APPLICATION_DEPLOY_VERSION}'.

      I think the 'Build parameters' column should show the resolved build parameter value, if based on an environment variable, or any other parameter substitution mechanism.

          [JENKINS-30129] 'Build Parameters' column displays uresolved environment variable

          Erik Godding Boye created issue -
          Erik Godding Boye made changes -
          Description Original: We are using environment variables (Jenkins->configuration->Global properties-->Environment variables) as default values of build parameters to our Jenkins deploy application builds:
          APPLICATION_DEPLOY_VERSION=x.y.z

          Somehow there is a requirement to indicate the latest deployed application version, per application deploy job. Introducing a 'Build parameters' column in the Jenkins view seems to fulfill this requirement. This works fine if the user overrides the default value of the version build parameter (${APPLICATION_DEPLOY_VERSION}).

          But if the user accepts the default value (${APPLICATION_DEPLOY_VERSION}), the 'Build parameters' column indicates that the latest build was invoked with the parameter value '${APPLICATION_DEPLOY_VERSION}'.

          I think the 'Build parameters' column should show the *resolved build parameter value*, if based on an environment variable, or any other parameter substitution mechanism.
          New: We are using environment variables (Jenkins->configuration->Global properties-->Environment variables) as default values of build parameters to our Jenkins deploy application builds:
          APPLICATION_DEPLOY_VERSION=x.y.z

          Somehow there is a requirement to indicate the latest deployed application version, per application deploy job. Introducing a 'Build parameters' column in the Jenkins view seems to fulfill this requirement. This works fine if the user overrides the default value of the version build parameter ($\{APPLICATION_DEPLOY_VERSION\}).

          But if the user accepts the default value ($\{APPLICATION_DEPLOY_VERSION\}), the 'Build parameters' column indicates that the latest build was invoked with the parameter value '$\{APPLICATION_DEPLOY_VERSION\}'.

          I think the 'Build parameters' column should show the *resolved build parameter value*, if based on an environment variable, or any other parameter substitution mechanism.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 165215 ] New: JNJira + In-Review [ 181880 ]
          Fred G made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Fred G made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            fredg Fred G
            erikgb Erik Godding Boye
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: