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

Jenkins Slaves launched with the incorrect environment variables

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • envinject-plugin
    • None
    • 1.89 of plugin used in Jenkins version 1.537

      Intermittent error where slaves launch with the incorrect environment variables. Tends to happen when there is a large demand for slaves to launch.

      Environment variables are set on Jenkins as required but do not seem to be injected to slaves at times causing builds to fail due to incorrect environment.

      Example:
      LD_LIBRARY_PATH set on master : /proj/litpadm200/tools/py-3pps-2.0/usr/lib64

      Failed Job environment:
      LD_LIBRARY_PATH : /app/openmotif/2.3.1/lib

          [JENKINS-23905] Jenkins Slaves launched with the incorrect environment variables

          Sam Xiao added a comment -

          +1

          We had the same issue on 1.89.

          Sam Xiao added a comment - +1 We had the same issue on 1.89.

          Mathieu Cantin added a comment -

          We had the same issue, but with a job.
          For example, a job was triggered at about the same time by two different parent jobs with different parameters (run A and run B). During the run B, we had environment variables corresponding to run A. After both runs, the "Environment variables" menu displays the correct parameters.

          On 1.90 in Jenkins version 1.565.1

          Mathieu Cantin added a comment - We had the same issue, but with a job. For example, a job was triggered at about the same time by two different parent jobs with different parameters (run A and run B). During the run B, we had environment variables corresponding to run A. After both runs, the "Environment variables" menu displays the correct parameters. On 1.90 in Jenkins version 1.565.1

          Andrew Cecil added a comment - - edited

          We are seeing the same issue almost every day. Unfortunately this causes the build to fail at the first step for us, before we can't even detect the problem and possibly do something about it. This only affects our Windows slaves, not Linux slaves. Similar to others, the "Environment variables" menu displays the correct values, but the slave process is obviously not seeing them. No errors or useful messages are seen in either the build log or the default jenkins system log.

          On 1.92.1 in Jenkins version 1.638.

          Andrew Cecil added a comment - - edited We are seeing the same issue almost every day. Unfortunately this causes the build to fail at the first step for us, before we can't even detect the problem and possibly do something about it. This only affects our Windows slaves, not Linux slaves. Similar to others, the "Environment variables" menu displays the correct values, but the slave process is obviously not seeing them. No errors or useful messages are seen in either the build log or the default jenkins system log. On 1.92.1 in Jenkins version 1.638.

            gbois Gregory Boissinot
            edarbyr Monty Byrnes
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: