CruiseControl integration: GETLABEL error

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
sanin
Posts: 9
Joined: Tue Jan 17, 2006 6:45 pm

CruiseControl integration: GETLABEL error

Post by sanin » Fri Mar 17, 2006 10:14 am

Integrating Vault with CC.NET:

I get the error where GETLABEL command CC tries to run fails with the following message:


3/17/2006 11:14:31 AM: [c360 Products:Debug]: Attempting to start process [c:\program files\sourcegear\vault client\vault.exe ] in working directory [C:\c360\build\latest\src] with arguments [getlabel $/MainTrunk.v3/Products.v3 3.0.5.56 -merge overwrite -performdeletions removeworkingcopy -setfiletime checkin -makewritable -host vault.local -user first.last -password *** -repository "V3"]
3/17/2006 11:14:32 AM: [CruiseControl Server:Debug]:
3/17/2006 11:14:32 AM: [CruiseControl Server:Debug]:
3/17/2006 11:14:32 AM: [CruiseControl Server:Debug]: usage: GETLABEL requires either -destpath or -labelworkingfolder to be set
3/17/2006 11:14:32 AM: [CruiseControl Server:Debug]:

It looks like Vault does not kraft a proper Vault command.

Any ideas?

The cc.net.config node for vault looks like this:

<sourcecontrol type="vault" autoGetSource="true" applyLabel="true">
<executable>c:\program files\sourcegear\vault client\vault.exe </executable>
<username>first.last</username>
<password>***</password>
<host>vault.local</host>
<repository>V3</repository>
<folder>$/MainTrunk.v3/Products.v3</folder>
<ssl>false</ssl>
<useWorkingDirectory>true</useWorkingDirectory>
<workingDirectory>C:\build\latest\src</workingDirectory>
</sourcecontrol>

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Fri Mar 17, 2006 11:25 am

This is a known issue in the 1.0* release of CruiseControl.NET. (http://jira.public.thoughtworks.org/browse/CCNET-614).

There are two options here:

1) Don't use applyLabel and useWorkingFolder together.

2) Run a pre-release version of CruiseControl.NET, which is what we're doing internally. 1.1.0.2239 is the last build to have a Vault-specific fix in it. The latest builds are here: http://ccnetlive.thoughtworks.com/CCNet-builds/
Ian Olsen
SourceGear

Post Reply