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

Build step names should allow for variables

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • vagrant-plugin
    • None

      Vagrant build steps like 'Provision' and 'Execute ssh' should allow for the use of environment variable references to make jobs that use them more useful (like in a matrix build environment that uses a single vagrant file for many machines).

      Currently, all fields are interpreted at face value - $WORKSPACE does not get expanded, which is particularly problematic when combined with https://issues.jenkins-ci.org/browse/JENKINS-26326

          [JENKINS-28798] Build step names should allow for variables

          kenorb added a comment - - edited

          Not sure what you mean, but I've used variable in Vagrant VM name and it was expanded. Or do you mean in different place?

          kenorb added a comment - - edited Not sure what you mean, but I've used variable in Vagrant VM name and it was expanded. Or do you mean in different place?

          edward no added a comment -

          please provide an example, i tried all of the following:

          • $BUILD_TAG
          • ${BUILD_TAG}
          • ${env.BUILD_TAG}

          the error is always similar:
          [ vagrant ]: java.io.IOException: Process working directory '/.jenkins/workspace/vagrant-test-2/${env.WORKSPACE}' doesn't exist!

          edward no added a comment - please provide an example, i tried all of the following: $BUILD_TAG ${BUILD_TAG} ${env.BUILD_TAG} the error is always similar: [ vagrant ]: java.io.IOException: Process working directory '/.jenkins/workspace/vagrant-test-2/${env.WORKSPACE}' doesn't exist!

            Unassigned Unassigned
            gleebix patrick crews
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: