NantContrib Help with 3.5

brydon · Post by **brydon** » Tue Aug 15, 2006 9:32 am

I realize this isn't a support forum for NantContrib, however, we've had a rash of issues with our build since moving to Vault 3.5. The latest appears to be related to NantContrib. I don't believe NantContrib binds directly to VaultClientOperationsLib but I could be wrong. Any advice is greatly appreciated....

VaultClientOperationsLib.GetLatestVersionFailedException: Exception of type Vaul
tClientOperationsLib.GetLatestVersionFailedException was thrown.
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(GetFileInfo
[] infos, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType
merge, Boolean updateHiddenFilesOnly, String ancestorFullPath, Boolean flat, Str
ing ancestorDiskPath, OverwritePrompt PromptData, Boolean isLabelGet, String cur
rentPathToLabelItem, Int64 labelID, Boolean isRetry, Boolean isGetByDisplayVersi
on)
at VaultClientOperationsLib.ClientInstance.Get(VaultClientFile[] files, Boole
an forceLatest, MakeWritableType makeWritable, SetFileTimeType setFileTime, Merg
eType merge, OverwritePrompt PromptData)
at VaultClientOperationsLib.ClientInstance.Get(VaultClientFile file, Boolean
forceLatest, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeTy
pe merge, OverwritePrompt PromptData)
at NAnt.Contrib.Tasks.SourceGearVault.vaultcheckout.CheckOut(String fileName)

at NAnt.Contrib.Tasks.SourceGearVault.vaultcheckout.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.TaskContainer.ExecuteChildTasks()
at NAnt.Core.Tasks.LoopTask.ExecuteChildTasks()
at NAnt.Core.Tasks.LoopTask.DoWork(String[] propVals)
at NAnt.Core.Tasks.LoopTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
at NAnt.Core.Tasks.CallTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.TaskContainer.ExecuteChildTasks()
at NAnt.Core.Tasks.IfTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
at NAnt.Core.Project.Execute()
at NAnt.Core.Project.Run()

Post by **jclausius** » Tue Aug 15, 2006 9:49 am

Does the Vault Server Log indicate any type of version mismatch?

brydon · Post by **brydon** » Tue Aug 15, 2006 10:07 am

No, there's nothing out of the ordinary there, just basic logins and logouts listed.

brydon · Post by **brydon** » Tue Aug 15, 2006 10:35 am

So is this a version issue in that Nant.Contrib is somehow referencing and using an old copy of VaultClientOperationsLib or should I be chasing down a different path to solve this?

ian_sg · Post by **ian_sg** » Tue Aug 15, 2006 11:19 am

Vault's NAnt tasks are not distributed with the NAntContrib tasks, they're just in the NAnt.Contrib.Tasks namespace. That's why you see that in your stack trace, it has nothing to do with any interaction with the NAntContrib tasks. So this problem shouldn't have anything to do with NAntContrib.

brydon · Post by **brydon** » Tue Aug 15, 2006 11:57 am

Based on a quick look at the NantContrib source that's what I figured. The only problem with that is that I still have my error, no build, and I'm not sure what to try next?

Any thoughts appreciated.....

ian_sg · Post by **ian_sg** » Tue Aug 15, 2006 12:12 pm

Heh sorry, I guess an actual suggestion for your problem would have been helpful.

If you enable nant verbose logging the Vault task will spit out the message that goes along with the get failure. The -l switch with a file turns on logging and the -v makes it verbose, e.g.

Code: Select all

nant.exe [whatever you have now] -l:mylogfile.txt -v

brydon · Post by **brydon** » Tue Aug 15, 2006 12:23 pm

The log file contains the exact same information and stacktrace I posted to start this off, nothing further was dumped to the log.

ian_sg · Post by **ian_sg** » Tue Aug 15, 2006 12:36 pm

If you have verbose turned on, there should be a message just above the stack trace indicating why the get failed, in a format similar to this:

Code: Select all

[vaultcheckout] Vault:  ...lots of ordinary messages...
[vaultcheckout] Vault:  failure message here
Exception stack trace here

brydon · Post by **brydon** » Tue Aug 15, 2006 1:58 pm

I swear there's nothing like that. It's strange because other checkouts are working and we're able to get source so I know nant is using vault effectively. I'm able to build if I comment out the offending tasks but that's far from a resolution.

any other ideas, shot away...