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

environmentVariables: from configuration file are added case-insensitive, preventing variables with different casing from being set

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • swarm-plugin
    • None
    • Linux

      When setting different variables (HTTP_PROXY and http_proxy, for example), only the one that's listed first in the configuration file under "environmentVariables:" is actually set on the node (verified with a simple job that runs the "env" command from a shell step). If order is changed, the other one wins.

      The expected behavior is that BOTH variables are set. Please fix.

            Unassigned Unassigned
            dhs Dirk Heinrichs
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: