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

          patrick crews created issue -
          kenorb made changes -
          Link New: This issue is related to JENKINS-33025 [ JENKINS-33025 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 163657 ] New: JNJira + In-Review [ 181326 ]

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

              Created:
              Updated: