History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-848
Type: Bug Bug
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Major Major
Assignee: Robin Shen
Reporter: Alexey Shumkin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Workspace of Windows build agent node is messed up

Created: 05/Mar/11 11:20 AM   Updated: 06/Mar/11 11:34 PM
Component/s: None
Affects Version/s: 3.1.24
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment:
Operating System Linux 2.6.35.11-83.fc14.i686, i386
JVM OpenJDK Client VM 19.0-b09, Sun Microsystems Inc.
QuickBuild Version 3.1.24 - Thu Mar 03 11:04:54 MSK 2011

QB Build Agent - Windows 2003 Server R2


 Description  « Hide
I have root's workspace as "/var/data/qb/workspace/${configuration.name}"
Let I have configs root/child-1/child-2/child-3 with "inherited.." workspace settings
Workspaces are
/var/data/qb/workspace/child-1
/var/data/qb/workspace/child-2
/var/data/qb/workspace/child-3

I run build agent on Windows (installed in C:\Program Files\QBuildAgent)
Then I go to workspace tab, choose that node and what I see in node's workspace value?
for child-1 - C:\Program Files\QBuildAgent\workspace\var\data\qb\workspace\child-1
for child-2 - C:\Program Files\QBuildAgent\workspace\var\data\qb\workspace\child-2\var\data\qb\workspace\child-2
for child-3 - C:\Program Files\QBuildAgent\workspace\var\data\qb\workspace\child-3\var\data\qb\workspace\child-3\var\data\qb\workspace\child-3

for the test I ran build agent on the same Linux server
all workspaces were the same as expected -
/var/data/qb/workspace/child-1
/var/data/qb/workspace/child-2
/var/data/qb/workspace/child-3

For the test I changed workspace settings of configurations for different items and values of the list . Nothing helped (except "Use config ID..." but that is not what I want)

 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [06/Mar/11 11:34 PM]
This is because that the path "/var/data/qb/workspace" is not treated as absolute on Windows. To solve the problem, please define the node attribute "workspaceRoot" on each node, for example on Windows, it might be "c:\data\qb\workspace", and on linux, it might be "/var/data/qb/workspace".
Then change the workspace setting of root configuration to use below:
${node.getAttribute("workspaceRoot")}/${configuration.name}

(You might need to replace "configuration.name" with "current.name" due to previous issue you created)