-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Windows
I've been asked to re-implement a big test process as a matrix job on our Hudson ( 1.355 )
I've noticed that when a matrix job is started on a Windows node some of the environment variables are set incorrectly, for example:
WORKSPACE=d:\hudson\workspace\tmp_matrix\label/spare0/test_group/g/test_number/1/test_sample_size/10
I made a matrix job which does nothing more than run the Windows "set" command - as you can see from the partial output above the environment variable contains both Windows and UNIX style path-separator slashes. Any process (such as mine ) which rely on the WORKSPACE environment variable being a correct path on the system will fail.
I suggest that this environment variable needs to use an OS-spesific method to form the paths.
- duplicates
-
JENKINS-5084 WORKSPACE env variable is incorrect for matrix project on windows slaves
-
- Open
-
[JENKINS-6393] WORKSPACE environment variable set incorrectly on a matrix job running on a Windows node
Description |
Original:
I've been asked to re-implement a big test process as a matrix job on our Hudson ( 1.327 ), which I know is not the latest version. I've noticed that when a matrix job is started on a Windows node some of the environment variables are set incorrectly, for example: WORKSPACE=d:\hudson\workspace\tmp_matrix\label/spare0/test_group/g/test_number/1/test_sample_size/10 I made a matrix job which does nothing more than run the Windows "set" command - as you can see from the partial output above the environment variable contains both Windows and UNIX style path-separator slashes. Any process (such as mine ) which rely on the WORKSPACE environment variable being an existing path on the system will fail. I suggest that this environment variable needs to use an OS-spesific method to form the paths. |
New:
I've been asked to re-implement a big test process as a matrix job on our Hudson ( 1.355 ) I've noticed that when a matrix job is started on a Windows node some of the environment variables are set incorrectly, for example: WORKSPACE=d:\hudson\workspace\tmp_matrix\label/spare0/test_group/g/test_number/1/test_sample_size/10 I made a matrix job which does nothing more than run the Windows "set" command - as you can see from the partial output above the environment variable contains both Windows and UNIX style path-separator slashes. Any process (such as mine ) which rely on the WORKSPACE environment variable being a correct path on the system will fail. I suggest that this environment variable needs to use an OS-spesific method to form the paths. |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Link | New: This issue duplicates JENKINS-5084 [ JENKINS-5084 ] |
Component/s | New: matrix-project [ 18765 ] | |
Component/s | Original: matrix [ 15501 ] |
Workflow | Original: JNJira [ 136488 ] | New: JNJira + In-Review [ 204063 ] |