• Type: Bug
• Resolution: Incomplete
• Priority: Major
• Component/s: core
• Labels:

  • configuration
  • jenkins
  • slave
• Environment:

  Hide

  java.runtime.name Java(TM) SE Runtime Environment
  java.runtime.version 1.7.0_03-b05
  java.specification.name Java Platform API Specification
  java.specification.vendor Oracle Corporation
  java.specification.version 1.7
  java.vendor Oracle Corporation
  java.vendor.url http://java.oracle.com/
  java.vendor.url.bug http://bugreport.sun.com/bugreport/
  java.version 1.7.0_03
  java.vm.info mixed mode
  java.vm.name Java HotSpot(TM) 64-Bit Server VM
  java.vm.specification.name Java Virtual Machine Specification
  java.vm.specification.vendor Oracle Corporation
  java.vm.specification.version 1.7
  java.vm.vendor Oracle Corporation
  java.vm.version 22.1-b02
  line.separator
  os.arch amd64
  os.name Windows Server 2008 R2
  os.version 6.1
  path.separator ;
  sun.arch.data.model 64

  Show

  java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_03-b05 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_03 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 22.1-b02 line.separator os.arch amd64 os.name Windows Server 2008 R2 os.version 6.1 path.separator ; sun.arch.data.model 64

[JENKINS-15397] Slave Nodes environment properties are not set correctly from Jenkins GUI

Collapse comment: Daniel Beck added a comment - 2014-05-21 15:40

Daniel Beck added a comment - 2014-05-21 15:40

Report does not mention which Jenkins version this occurs with. Also, it's quite old by now, so closing this as incomplete. If it still occurs on recent Jenkins versions, feel free to reopen or file a new issue.

Also, answers to the following questions are also important for further investigation:

• Are you trying to override the automatically created env variables manually, or do you mean they're not up to date?
• How is the slave started?
• Do you configure env variables in the node configuration?
• Did you rename and/or change labels recently?
  • Did you afterwards not disconnect the slave?
• How can this be reproduced?
  • Can it be reproduced in recent Jenkins versions?

Expand comment: Daniel Beck added a comment - 2014-05-21 15:40

Daniel Beck added a comment - 2014-05-21 15:40 Report does not mention which Jenkins version this occurs with. Also, it's quite old by now, so closing this as incomplete. If it still occurs on recent Jenkins versions, feel free to reopen or file a new issue. Also, answers to the following questions are also important for further investigation: Are you trying to override the automatically created env variables manually, or do you mean they're not up to date? How is the slave started? Do you configure env variables in the node configuration? Did you rename and/or change labels recently? Did you afterwards not disconnect the slave? How can this be reproduced? Can it be reproduced in recent Jenkins versions?