-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.609.1
distfork-plugin 1.3
java8
master on Windows.
If a node has been given node properties such as "PATH" or "PATH+FOOBAR" then these are ignored by distfork which results in the distfork command not using the environment on the node and not being able to be built.
The hacky workaround is to set up these variables as system properties on the machine.
steps to reproduce
1) install cygwin in c:\somewhere\not\in\the\path on windows
2) setup the node to have PATH+CYGWIN=c:\somewhere\not\in\the\path node property.
3) create a freestyle job - execute windows command -> env
4) run a distfork command dist-fork -l windows cmd.exe /c
expected results
Both the freestyle and the distform have a path that contains c:\somewhere\not\in\the\path
actual results
- The freestyjob has the modified path
- The distfork plugin has the unmodified path
- attempting to run a command with distfork that is in c:\somewhere\not\in\the\path fails with command not found
[JENKINS-30768] distfork does not setup environment on the slave correctly.
| Environment |
Original:
Jenkins 1.609.1 java8 master on Windows. |
New:
Jenkins 1.609.1 distfork-plugin 1.3 java8 master on Windows. |
| Description |
Original:
If a node has been given node properties such as "PATH" or "PATH+FOOBAR" then these are ignored by distfork which results in the distfork command not using the environment on the node and not being able to be built. The hacky workaround is to set up these variables as system properties on the machine. h2. steps to reproduce 1) install cygwin in c:\somewhere\not\in\the\path on windows 2) setup the node to have PATH+CYGWIN=c:\somewhere\not\in\the\path node property. 3) create a freestyle job - execute windows command -> {{env}} 4) run a distfork command {{dist-fork -l windows cmd.exe /c h2. expected results h2. expected results Both the freestyle and the distform have a path that contains {{c:\somewhere\not\in\the\path}} h2. actual results * The freestyjob has the modified path * The distfork plugin has the *un*modified path |
New:
If a node has been given node properties such as "PATH" or "PATH+FOOBAR" then these are ignored by distfork which results in the distfork command not using the environment on the node and not being able to be built. The hacky workaround is to set up these variables as system properties on the machine. h2. steps to reproduce 1) install cygwin in c:\somewhere\not\in\the\path on windows 2) setup the node to have PATH+CYGWIN=c:\somewhere\not\in\the\path node property. 3) create a freestyle job - execute windows command -> {{env}} 4) run a distfork command {{dist-fork -l windows cmd.exe /c h2. expected results h2. expected results Both the freestyle and the distform have a path that contains {{c:\somewhere\not\in\the\path}} h2. actual results * The freestyjob has the modified path * The distfork plugin has the *unmodified* path |
| Description |
Original:
If a node has been given node properties such as "PATH" or "PATH+FOOBAR" then these are ignored by distfork which results in the distfork command not using the environment on the node and not being able to be built. The hacky workaround is to set up these variables as system properties on the machine. h2. steps to reproduce 1) install cygwin in c:\somewhere\not\in\the\path on windows 2) setup the node to have PATH+CYGWIN=c:\somewhere\not\in\the\path node property. 3) create a freestyle job - execute windows command -> {{env}} 4) run a distfork command {{dist-fork -l windows cmd.exe /c h2. expected results h2. expected results Both the freestyle and the distform have a path that contains {{c:\somewhere\not\in\the\path}} h2. actual results * The freestyjob has the modified path * The distfork plugin has the *unmodified* path |
New:
If a node has been given node properties such as "PATH" or "PATH+FOOBAR" then these are ignored by distfork which results in the distfork command not using the environment on the node and not being able to be built. The hacky workaround is to set up these variables as system properties on the machine. h2. steps to reproduce 1) install cygwin in {{c:\somewhere\not\in\the\path}} on windows 2) setup the node to have {{PATH+CYGWIN=c:\somewhere\not\in\the\path}} node property. 3) create a freestyle job - execute windows command -> {{env}} 4) run a distfork command {{dist-fork -l windows cmd.exe /c}} h2. expected results Both the freestyle and the distform have a path that contains {{c:\somewhere\not\in\the\path}} h2. actual results * The freestyjob has the modified path * The distfork plugin has the *unmodified* path * attempting to run a command with distfork that is in {{c:\somewhere\not\in\the\path}} fails with command not found |
| Workflow | Original: JNJira [ 165895 ] | New: JNJira + In-Review [ 182190 ] |