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.