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

Environment variables on Windows are all lowercase since 2.50

XMLWordPrintable

      Since updating to Jenkins 2.50 ANT builds that use environment variables fail on windows slaves because lots of environment variables are now all lowercase.

      Using environment variables in ANT is case sensitive.

      Variables that come from the system are all lowercase (COMPUTERNAME, Path, SystemDrive, SERVICE_ID, ...) and variables that come from Jenkins are as usual (NODE_NAME, BUILD_ID, ...).

      SERVICE_ID is interesting because it is not set on the system, used to be all uppercase is now also all lowercase.

       SSH Slaves are not affected. Windows slaves use Java Web Start and jenkins-slave.exe as a service.

      Researching I found this which may be related:

      https://social.msdn.microsoft.com/Forums/vstudio/en-US/031707fc-b95d-407c-aadf-5dc1bca69c94/system-variables-lower-case-ant-issue?forum=tfsbuild

            oleg_nenashev Oleg Nenashev
            cobexer Ing. Christoph Obexer
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: