matrix build custom workspace

[Slide]

I am trying to setup a matrix build. I have a custom workspace setup in my job, but when the job actually runs, there is something appended to the path I specify. I can't seem to find an option that turns this behavior off, is this possible?

c:/ccviews/myview_SOMENODE becomes c:/ccviews/myview_SOMENODE/label/slave

Thanks,

slide

--
slide-o-blog
http://slide-o-blog.blogspot.com/

[Jan Seidel]

Hi Slide,

have you tried to restrict where to run the job?
This looks to me like a modification caused as the job runs on a slave
node and not the master.

Take care
Jan

[Slide]

I am currently using restricting to run on a specific slaves, but I'm trying to get it to work with matrix builds. I don't see the same appending behavior with just restricting, only on the matrix builds.

[Dr. Simon Wiest]

Hi Slide,

a 'custom workspace' in matrix project is a custom parent directory that
will contain all the runs for each matrix combination.

Usually the combinations must be separated from each other, e.g. because
they are built in parallel. Therefore the layout of the subdirectories
in that custom workspace looks like in the following example:

Assuming you have an axis FRUIT {Apple, Peach} and an axis COLOR
{yellow, red}:

My_Custom_Workspace_Directory
--FRUIT
----Apple
------COLOR
--------yellow [This is the workspace of "Apple/yellow"]
--------red [This is the workspace of "Apple/red"]
--- Peach
------COLOR
--------yellow [This is the workspace of "Peach/yellow"]
--------red [This is the workspace of "Peach/red"]

As slaves are technically just another axis of a matrix project, they
will create a subdirectory structure as described above.

If your _really_ want to map all combinations of your matrix to a single
directory, you may try changing to parent directories exactly twice per
axis in your build scripts (yes, it's lame...;O)).

Cheers,
Simon.
--
Slide (16.06.2011 16:24):