[#QB-453] Quickbuild 2.x User Agent incorrectly builds workspace directory path (and it is too long for Windows to delete)

QuickBuild

Quickbuild 2.x User Agent incorrectly builds workspace directory path (and it is too long for Windows to delete)

Created: 13/Oct/09 04:50 PM Updated: 15/Oct/09 03:22 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
Environment:	Windows XP SP3

Description

« Hide

When using the User Agent to run proof builds on the Quickbuild server, the User Agent incorrectly builds the workspace path locally on my Windows system for the given build. Because of this, the path is actually too long for Windows to delete, and subsequent builds will fail. Here is an example path:

For a path that should likely be -->
C:\Development\Tools\quickbuild\useragent\workspace\build\workspaces\quickbuild\root\level1\level2\projectName

The User Agent actually constructs it as -->
C:\Development\Tools\quickbuild\useragent\workspace\build\workspaces\quickbuild\root\build\workspaces\quickbuild\root\level1\build\workspaces\quickbuild\root\level1\level2\build\workspaces\quickbuild\root\level1\level2\projectName

The User Agent is installed in "C:\Development\Tools\quickbuild\useragent\" on my local machine. Note how it repeats the "\build\workspaces\quickbuild\" portion for each level in the path.

Thanks,
Kurt

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [14/Oct/09 12:45 AM]

Hi Kurt,

Can you tell how the workspace path property is defined in below configurations?
1. root
2. root/level1
3. root/level1/level2
4. root/level1/level2/projectName

And if the workspace path definition uses certain attributes defined in the user agent node, please list value of those attributes also.

Thanks

[ Permlink | « Hide ]

Kurt Legerlotz [14/Oct/09 11:28 AM]

Hi Robin,

First, thanks for your quick response. Second, the workspace path property is only defined once, at the root level. It is the following:

/build/workspaces/quickbuild/${current.pathName}

Does the pathName include the entire workspace path when it is referenced in child configurations? Why don't we see this behavior on the server then?

Thanks,
Kurt

[ Permlink | « Hide ]

Robin Shen [15/Oct/09 03:22 AM]

While Linux recognizes this as an absolute path, JVM on Windows treat this path as a relative path. Write "workspace path" property as below will solve the problem:

${node.getAttribute("os.name").contains("Windows")?
"C:/build/workspaces/quickbuild/" + current.pathName:
"/build/workspaces/quickbuild/" + current.pathName}