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

${WORKSPACE} variable doesn't use my specific workspace directory anymore in a build step

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: envinject-plugin
    • Labels:
      None
    • Environment:
      Jenkins on Linux
    • Similar Issues:

      Description

      With version 0.26, when I specify a specific project workspace (in project advanced options), if I use ${WORKSPACE} in a build step (in my case a shell script), the variable is replaced but it is replace by the default workspace value, not the one I specified previously.

        Attachments

          Activity

          korg Philippe Larouche created issue -
          gbois Gregory Boissinot made changes -
          Field Original Value New Value
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          marcelhuber Marcel Huber made changes -
          Resolution Fixed [ 1 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          marcelhuber Marcel Huber made changes -
          Attachment envinject_test.xml [ 21232 ]
          gbois Gregory Boissinot made changes -
          Priority Blocker [ 1 ] Minor [ 4 ]
          marcelhuber Marcel Huber made changes -
          Attachment envinject_test.xml [ 21342 ]
          gbois Gregory Boissinot made changes -
          Status Reopened [ 4 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 142299 ] JNJira + In-Review [ 190063 ]

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              korg Philippe Larouche
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: