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

Environment variables on Windows are all lowercase since 2.50

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            The fix has been integrated towards 2.53

            Show
            oleg_nenashev Oleg Nenashev added a comment - The fix has been integrated towards 2.53
            Hide
            nkjensen Niels Kristian Jensen added a comment -

            Great, I'm looking forward to test it soon. Thank you

            Show
            nkjensen Niels Kristian Jensen added a comment - Great, I'm looking forward to test it soon. Thank you
            Hide
            jesperjensen Jesper Jensen added a comment -

            Would it be possible to make a guide on how to upgrade both master and windows slaves with this change, somewhat pain less. E.G. where do I find the jenkins-slave.exe and the jenkins.exe so that I can copy them to the correct places?

            Show
            jesperjensen Jesper Jensen added a comment - Would it be possible to make a guide on how to upgrade both master and windows slaves with this change, somewhat pain less. E.G. where do I find the jenkins-slave.exe and the jenkins.exe so that I can copy them to the correct places?
            Show
            oleg_nenashev Oleg Nenashev added a comment - Jesper Jensen https://github.com/jenkinsci/windows-slave-installer-module#upgrading-old-agents I will link it in the changelog
            Hide
            nkjensen Niels Kristian Jensen added a comment -

            The problem has been fixed at least since 2.61

            Show
            nkjensen Niels Kristian Jensen added a comment - The problem has been fixed at least since 2.61

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                cobexer Christoph Obexer
              • Votes:
                4 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: