• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: envfile-plugin
• Labels:

  • envinject-plugin
  • plugin
• Environment:

  Jenkins 2.20
  envinject 2.0

1. 

   jenkins_rdp_view.jpg

   69 kB

   2017-05-10 13:10

2. 

   jenkins_console_output_view.jpg

   73 kB

   2017-05-10 13:09

[JENKINS-44186] WIndows System Environment Variables Not updating in until restart

Nathan Turner created issue - 2017-05-10 13:27

Nathan Turner made changes - 2017-05-10 13:28

Labels

Original: plugin

New: envinject-plugin plugin

Nathan Turner made changes - 2017-05-10 13:31

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Nathan Turner made changes - 2017-05-10 13:31

Status

Original: In Progress [ 3 ]

New: Open [ 1 ]

Nathan Turner made changes - 2017-05-10 15:57

Description

Original: We have a python script ( using py2exe ) that modifies System Environment Variables and recently noticed that on our Slaves calling SET in Jenkins vs SET in a shell on the slave shows different results.  The only way we have found to make the JENKINS System Env Variables to change is to physically re-start that machine. The 2 images show how Jenkins and the system disagree on what this var ( V_PROJECT_WORKSPACE_DIR ) is set to. jenkins_rdp_view.jpg : The remote view of a NEW command window jenkins_console_output_view.jpg : A script running on that slave that show what it sees.

New: We have a python script ( using py2exe ) that modifies System Environment Variables and recently noticed that on our Slaves calling SET in Jenkins vs SET in a shell on the slave shows different results.  The only way we have found to make the JENKINS System Env Variables to change is to physically re-start that machine. The 2 images show how Jenkins and the system disagree on what this var ( V_PROJECT_WORKSPACE_DIR ) is set to. jenkins_rdp_view.jpg : The remote view of a NEW command window jenkins_console_output_view.jpg : A script running on that slave that show what it sees. EDIT: After thinking on this more, and talking with some Programmers the theory is that Jenkins is in a VM and thus snap-shots the system then passes those variables down. we use setx KEY VALUE, and that sets registry, but doesn't change the local environment. Maybe this should be a feature, but a way to 're-snap' the System's Environment variables if prompted to.

Nathan Turner made changes - 2017-05-10 15:57

Priority

Original: Major [ 3 ]

New: Minor [ 4 ]