CC.NET broken with Vault 4

bnott · Post by **bnott** » Mon Jun 11, 2007 7:05 am

After upgrading to Vault 4 from 3.5, the vault source control block from CC.NET is now reporting that "Vault user has no working folder set for $/Applications/ShipWorks/Trunk in repository and no working directory has been specified.".

The only thing that has changed on the system from when it worked, until now, is the vault upgrade. I can verify that there is a working directory for the folder, and in fact immediately before the error occurs I run Vault with SETWORKINGFOLDER.

I looked through SourceFourge at Vault3.cs and I think I may see the problem. It looks like perhaps in Vault 3.5, the "reposfolder" and "localfolder" XML result nodes for the "listworkingfolder" command were actually attributes, not nodes. However, in 4 they are returned as nodes, not attributes. So the "GetWorkingFolder" function in the Vault3 class never finds the working folder, since its looking for an attribute and not a child node. At least thats my guess.

I appreciate your help in advance to get our build working again.

Thanks,
Brian

bnott · Post by **bnott** » Mon Jun 11, 2007 7:20 am

Setting workingDirectory and useWorkingDirectory in the cc.net config seems to get it going. It would be nice not to have to do that though - so if you could let me know when\if it gets fixed, that would great.

Thanks,
Brian

ian_sg · Post by **ian_sg** » Mon Jun 11, 2007 8:39 am

Thanks for the report, Brian. We'll see if we can get the output in a more backward-compatible format here.

Post by **jeremy_sg** » Mon Jun 11, 2007 12:40 pm

This will be fixed in the upcoming 4.0.1.