I got three projects integrating on CruiseControl.Net. One is to just update the ccnet.config file when a new version is committed. The other two are the trunk version of my projects, shared libraries and an application suite, and they were working fine.
I tried to add a project to build a branch version of my applications. After the ccnet service restarted, the new project tried to build an immediately failed with an exception.
Looking at the logs, both the trunk and branch of the applications tried to logon at once and failed. They retried and it looks like succeeded, but then BOTH projects began giving me another exception. The branch hasn't even pulled down it's first copy of the source.
My repo is like this:
$/app/trunk
$/app/branches/2.2.5 (I have previous versions too, but won't be building them)
Here's the log from cc.net.
2011-01-12 19:40:19,290 [app - Trunk:INFO] Project: 'app - Trunk' is added to queue: 'app - Trunk' in position 0. Requestsource : continuous ()
2011-01-12 19:40:19,390 [app - Trunk:INFO] Queue: 'app - Trunk' is attempting to be in-use, trying to lock related queues
2011-01-12 19:40:19,390 [app - Trunk:INFO] Project: 'app - Trunk' is first in queue: 'app - Trunk' and shall start integration.
2011-01-12 19:40:19,391 [app - Trunk:DEBUG] In VaultProVaultSourceControl.GetModifications()
2011-01-12 19:40:19,400 [app - Trunk:DEBUG] Loading Client tree information for DartmouthJournals
2011-01-12 19:40:19,412 [app - Trunk:ERROR] Unable to set active repository: System.ArgumentNullException: Value cannot be null.
Parameter name: path2
at System.IO.Path.Combine(String path1, String path2)
at VaultClientOperationsLib.TreeCache..ctor(Int32 repID, String username, String uniqueRepositoryID, String localStoreBasePath, ClientInstance ci)
at VaultClientOperationsLib.ClientInstance.SetActiveRepositoryID(Int32 id, String username, String uniqueRepositoryID, Boolean doRefresh, Boolean updateKnownChangesAll)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.VaultProClient.ConnectToRepository(String Repository)
2011-01-12 19:40:19,414 [app - Trunk:ERROR] Refresh() failed.
2011-01-12 19:40:19,415 [app - Trunk:DEBUG] Unloading Client tree information.
2011-01-12 19:40:19,915 [app - Trunk:DEBUG] Garbage collecting.
2011-01-12 19:40:19,929 [app - Trunk:INFO] No modifications detected.
The same thing happens for the branch version as well, same messages and all.
Any ideas?
Thanks
Andy
CruiseControl.Net - Exceptions checking source
Re: CruiseControl.Net - Exceptions checking source
Hello, Andy.
It would help us to know which versions of Vault and CruiseControl you are using. From your log, it looks like you're using Vault Professional, but is it 5.1.0 or 5.1.1? And is it CCNet 1.4 or 1.5?
One thing I can recommend is that you look into CCNet's "Integration Queues" feature. It's very easy to set up, and it prevents the "everything-at-once" problem that you're experiencing. Details here:
http://confluence.public.thoughtworks.o ... ion+Queues
It looks like there's something else going on here, though, so please reply with your version info, and we'll let you know if we need anything else.
Thanks,
- Joe
It would help us to know which versions of Vault and CruiseControl you are using. From your log, it looks like you're using Vault Professional, but is it 5.1.0 or 5.1.1? And is it CCNet 1.4 or 1.5?
One thing I can recommend is that you look into CCNet's "Integration Queues" feature. It's very easy to set up, and it prevents the "everything-at-once" problem that you're experiencing. Details here:
http://confluence.public.thoughtworks.o ... ion+Queues
It looks like there's something else going on here, though, so please reply with your version info, and we'll let you know if we need anything else.
Thanks,
- Joe
Joe Ream
SourceGear Technical Support
SourceGear Technical Support
Re: CruiseControl.Net - Exceptions checking source
Hi Joe,
Thanks for your quick response.
I'm using CC.Net 1.5.7256.1. I'm also using the latest version of Vault Pro:
[1/13/2011 6:02:17 PM] Version Check: This Vault Professional client is version 5.1.1.19216
[1/13/2011 6:02:17 PM] Version Check: Your server is version 5.1.1.19216
I don't think integration queues are the answer; the problem isn't with the logons (I've seen many other threads, and it sounds like that's more or less fixed). I'm a single developer shop and so the only other logons is the CC.Net server, and I have a total of only four integrator projects. Should be a snap for Vault to handle I'd think.
Let me know if there's any other information I can provide. I haven't seen anything correlating in a Vault log, but I don't think verbose logging is enabled.
Thanks
Andy
Thanks for your quick response.
I'm using CC.Net 1.5.7256.1. I'm also using the latest version of Vault Pro:
[1/13/2011 6:02:17 PM] Version Check: This Vault Professional client is version 5.1.1.19216
[1/13/2011 6:02:17 PM] Version Check: Your server is version 5.1.1.19216
I don't think integration queues are the answer; the problem isn't with the logons (I've seen many other threads, and it sounds like that's more or less fixed). I'm a single developer shop and so the only other logons is the CC.Net server, and I have a total of only four integrator projects. Should be a snap for Vault to handle I'd think.
Let me know if there's any other information I can provide. I haven't seen anything correlating in a Vault log, but I don't think verbose logging is enabled.
Thanks
Andy
Re: CruiseControl.Net - Exceptions checking source
We would like to have you set up some special logging. So that we can provide you with what you need, could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support