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

Job-B ${WORKSPACE} has value of Job-A WORKSPACE

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      If Jenkins job "A" has a configured fstrigger-trigger, then some other Jenkins jobs "B" (not all) will inherit the job "A" value for their ${WORKSPACE} env-variable. Keeping job "A", but removing the fstrigger and restarting Jenkins, will solve the issue. Adding an explicit WORKSPACE to all "B"-jobs will solve the issue. Job "A" does not directly use the envinject plugin, but "B" jobs do.

        Attachments

          Activity

          Hide
          nnau Natalia Naumova added a comment -

          I see the same issue if job A uses scripttrigger plugin.

          Show
          nnau Natalia Naumova added a comment - I see the same issue if job A uses scripttrigger plugin.
          Hide
          zioschild Sven Appenrodt added a comment -

          Seems the problem can be reproduced only after the second run (but i'm not sure)
          The biggest problem is, the workspace of each job triggered by the fsp will be overwritten permanently. Example:

          Job A (fstrigger) -> Job B -> Job C
          Job 1 (normal time trigger) -> Job 2 -> Job C

          It doesnt matter if Job C is triggered by Job A or 1 - the WORKSPACE variable is set to "workspace\Job A" everytime.

          Show
          zioschild Sven Appenrodt added a comment - Seems the problem can be reproduced only after the second run (but i'm not sure) The biggest problem is, the workspace of each job triggered by the fsp will be overwritten permanently. Example: Job A (fstrigger) -> Job B -> Job C Job 1 (normal time trigger) -> Job 2 -> Job C It doesnt matter if Job C is triggered by Job A or 1 - the WORKSPACE variable is set to "workspace\Job A" everytime.
          Hide
          bakito Marc Brugger added a comment -

          I have the same Problem, The WORKSPACE variable of other Jobs gets overwritten as long the fstrigger is active on in other build.

          Show
          bakito Marc Brugger added a comment - I have the same Problem, The WORKSPACE variable of other Jobs gets overwritten as long the fstrigger is active on in other build.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              riccardo_gorza Riccardo Gorza
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: