Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

Workspace directory for windows build agent #3132

daneng ·
I'm trying to set up a windows build agent to be able to do visual studio builds.

We are currently running version 4.0.74 of QuickBuild.

The trouble is that the workspace directory automatically and without control adds "opt/var/quickbuild/workspace" to anything I try to set it to...

The build agent is installed at:
K:\developing\buildagent\

I am unable to get it to respect an absolute path, if I set "Use specified workspace directory" a path starting with a forward slash it just appends that path to the path. Setting it to "/test" results in: K:\developing\buildagent\workspace\var\opt\quickbuild\workspace/test

If I set it to an absolute windows path such as "K:\developing\buildagent\workspace" it changes that to:

K:\developing\buildagent\workspace\var\opt\quickbuild\workspace\k\developing\buildagent\workspace

This would not be so bad if it was not for our repository containing some deep folder paths which make the paths for some files to long for windows to handle...

What should I do to get around this?

Best regards,
Dan Engelbrecht
  • replies 5
  • views 3263
  • stars 0
daneng ·
Ok, so I'm currently working around this by specifying the working directory as "../../..".

Not pretty...

Dan
daneng ·
Well, that only worked for the first part.

Later on it inserts the ../../../ in a different way and the path to execute commands in the build step gets all messed up.

Seems like it *still* appends the "path from build configuration name" option even though I have stated an explicit path...

Giving up on that solution.
robinshen ADMIN ·
You may define the workspace path via some script for instance:
${node.getAttribute("os.name", "").toLowerCase().startsWith("win")? "K:\path\to\windows\workspace": "/path/to/linux/workspace"}
drdt ·
This sounds like an error in your configuration to me. Maybe one of your configurations still has a reference to the linux path?

What I did to set an alternate path location was
- set a variable "sysWorkspaceRoot" to "F:\quickbuild\workspaces"
- under advanced settings for the 'root' configuration, use this variable as the Workspace Directory Setting
- under advanced settings for the 'build' configuration, use the configuration name
- all child configurations of 'build', inherit from parent

This results in my path for every configuration being 'F:\quickbuild\workspaces\build\TEAM\PROJECT\...'
Now, I am only running on Windows, *and*, I am using version 6.0. But I am pretty sure this also worked when I was on version 4.

Using Robin's suggestion, you should be able to have different root paths for Windows and Linux. Another solution might be to define a user property on each slave box (and on the server), specifying the location of the workspace directory for that slave in the correct windows or linux format.
daneng ·
I will try the script solution.

I think this is related to the QuickBuild server running Linux and the QuickBuild node running windows.