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

Environment is not injected for each configuration in a multi-configuration project

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: envinject-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.446, EnvInject 1.11
    • Similar Issues:

      Description

      When using a property file with "Prepare an environment for the job" with a multi-configuration project, variables are not injected for each configuration.
      By looking at the console output, the environment is indeed injected at the master job level (the one launching a job for each configuration). however, it doesn't help as it seems that the environment is re-created for each configuration job.

        Attachments

          Activity

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              frederic_latour Frederic Latour
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: