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

EnvInject plugin sets global WORKSPACE variable to arbitrary workspace

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Upgraded from EnvInject 1.0 to 1.85 and builds stopped working correctly.

      Each build was using the wrong workspace, and all builds were trying to use this same incorrect workspace. The workspace was a valid workspace for a different job, but not the job that I was running. Each time I reloaded jenkins, the workspace changed but all builds still tried to use that same incorrect workspace.

      I had the following in my ant script:
      <property environment="env"/>
      <property name="job.wspath" value="${env.WORKSPACE}"/>

      job.wspath was being set to the workspace of the wrong job, because the WORKSPACE env variable was getting hosed by the new EnvInject.

      I downgraded EnvInject from 1.85 to 1.0 and the problem was resolved.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            gbois Gregory Boissinot
            Reporter:
            joel1234567 Joel Wheeler
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: