EnvInject - Conflicts between file names in home dir and the relative path

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Minor
    • Component/s: envinject-plugin
    • Environment:
      Jenkins ver. 1.642
      Environment Injector Plugin 1.90
      Setup with a build slave

      If a file exists in slave home directory, e.g. /home/jenkinsslave/env.properties, then injecting environment variables will fail, if the Properties File has the same name.

      Top level file exists:

      ...
      + cat env.properties
      VERSION=123
      [EnvInject] - Injecting environment variables from a build step.
      [EnvInject] - Injecting as environment variables the properties file path 'env.properties'
      [EnvInject] - Variables injected successfully.
      ...
      /home/jenkinsslave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3/bin/mvn versions:set -DnewVersion=$VERSION
      

      Top level file does not exist:

      ...
      + cat env.properties
      VERSION=123
      [EnvInject] - Injecting environment variables from a build step.
      [EnvInject] - Injecting as environment variables the properties file path 'env.properties'
      [EnvInject] - Variables injected successfully.
      ...
      /home/jenkinsslave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3/bin/mvn versions:set -DnewVersion=123
      

            Assignee:
            Oleg Nenashev
            Reporter:
            Stefan Kober
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: