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

Enivronment is not separated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • envinject-plugin
    • None

      The environment variables still spreads around the jobs. Try the following:

      • Configure a maven job
      • Use the Inject "Inject environment variables to the build process" checkbox and write something into the "Properties Content" box
      • Start the job

      You will notice the following (during the run of the maven job)

      • Start a free style job that prints all environment variables
      • It will print the injected variables from the maven job
      • Configure another maven job
      • Use the same injection method and the same variable to be injected
      • Start the job

      If the first job is still running, it will adept the environment from the second maven job!

            gbois Gregory Boissinot
            leovonklenze leovonklenze
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: