Error Diffing Labels

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

Moderator: SourceGear

Post Reply
eldi.espinosa
Posts: 6
Joined: Mon Jun 27, 2005 2:08 pm
Location: Seattle

Error Diffing Labels

Post by eldi.espinosa » Mon Jun 27, 2005 2:15 pm

Hello,
I'm getting an error diffing labels from command line. I am labeling trhe repository with a build number and later on generating change logs based on a diff between the previous label and the new one. I am using nant to automate the whole process but when I execute the command GETLABELDIFFS [repository] [old-label] [new-label] [conection options]. I get the error below (old-label not valid). I've tried executing the same command from command line inmediately after the error and I get a valid list of changes. Any help would be greatly appreciated.


<vault>
<error>
Invalid label: Build4.2.2.57

</error>
<exception>
System.ArgumentException: Invalid label: Build4.2.2.57

at VaultCmdLineClient.VaultCmdLineClient.GetLabelTimeStamps(String item, String label1, String label2, DateTime& timestamp1, DateTime& timestamp2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandGetLabelDiffs(String strReposPath, String strLabel1, String strLabel2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Tue Jun 28, 2005 8:17 am

I'm not sure what's going on. That error message only shows up when it can't find the label. Can you post the exact command line that you're using?

Guest

Post by Guest » Tue Jun 28, 2005 11:45 am

yeah the command I'm using is the following:

vault GETLABELDIFFS $/FOO/BAR/Current Build4.2.2.57 Build4.2.2.58 -host [HOSTNAME] -username [USER] -password [PASSWORD] -repository [BAZ]

I'm using Vault Client 3.0.7

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Tue Jun 28, 2005 12:43 pm

Your command line looks fine. Email me using the button below this post, and I'll see if we can track down the cause of this.

Post Reply