Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Platform: All, OS: All
Description
For Windows platform, if you execute Hudson in a directory with a space, the
option "Use existing dynamic view" doesn't work (its works for snapshot view)
started
[workspace] $ cleartool startview build_P_ChangeMgt_V3.2.1_int
[build_P_ChangeMgt_V3.2.1_int] $ cleartool chstream -generate
stream_ChangeMgt_V3.2.1_int@\P_ORC
Changed stream "stream_ChangeMgt_V3.2.1_int@\P_ORC".
[workspace] $ cleartool setcs -tag build_P_ChangeMgt_V3.2.1_int -stream
[build_P_ChangeMgt_V3.2.1_int] $ cleartool lsproject -cview -fmt %[mod_comps]Xp
Failed to create baseline: java.io.IOException: Cannot run program "cleartool"
(in directory "C:\Documents and Settings\s0011918\.hudson\jobs\test3
\workspace\build_P_ChangeMgt_V3.2.1_int"): CreateProcess error=267, The
directory name is invalid
finished: FAILURE
Ok, I am wrong.
The problem is not in the space for the HUDSON_HOME directory.
The problem is deeper.
In the case of existing dynamic view, you use, the command is cleartool
lsproject -cview -fmt %[mod_comps]Xp and this command is executed in
$WORKSPACE\dynViewName. The source code is the same for snapshot view
So, certainly, it’s will not work.
It’s a dynamic view, so the working directory should be like M:\dynViewName
How it’s works for your cases? Is there a special parametrization?
So, my solution is to not use the "-cview" argument and execute the command in
the workpace root with the "view" argument and the "dynViewName" like value