4.0.1 and CC.NET

bnott · Post by **bnott** » Tue Jun 19, 2007 10:40 am

I upgraded the server to vault 4.0.1.

The automatic build stopped automatically building. Checking the cc.net server log, I found this:

System.NullReferenceException: Object reference not set to an instance of an object.
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.VaultHistoryParser.EntryWithinRange(XmlNode node, DateTime from, DateTime to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.VaultHistoryParser.Parse(TextReader history, DateTime from, DateTime to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.ParseModifications(TextReader reader, DateTime from, DateTime to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.ParseModifications(ProcessResult result, DateTime from, DateTime to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault317.GetModificationsFromItemHistory(IIntegrationResult from, IIntegrationResult to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault317.GetModifications(IIntegrationResult from, IIntegrationResult to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.VaultVersionChecker.GetModifications(IIntegrationResult from, IIntegrationResult to)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications(ISourceControl sourceControl, IIntegrationResult lastBuild, IIntegrationResult thisBuild)
at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest request)
at ThoughtWorks.CruiseControl.Core.Project.Integrate(IntegrationRequest request)
at ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Integrate()

Any ideas on what I could do, or do I need to wait for a vault update?

Thanks,
Brian

Beth · Post by **Beth** » Tue Jun 19, 2007 1:00 pm

Can you check that project and the files involved and make sure that you can perform a Get on them to another location? That will help narrow down the issue.

bnott · Post by **bnott** » Tue Jun 19, 2007 1:05 pm

The get must be working - if I "Force" a build in CC.NET it does clean the folder and get the latest from vault.

However, if I leave CC.NET to autoamtically check for modifications, it gets endlessly stuck in the "CheckingForModifications" status, because it always gets that exception.

Did I answer your question?

ian_sg · Post by **ian_sg** » Tue Jun 19, 2007 2:24 pm

I was able to reproduce this problem.

Beyond waiting for an update, you can point CC.NET at a version 4.0.0 version of vault.exe.

If all of this is running on your vault server, I'd recommend installing the 4.0.0 client on another machine and copying the client directory to the CC.NET server in an alternate location, then altering your ccnet.config to use that vault.exe.

bnott · Post by **bnott** » Tue Jun 19, 2007 3:15 pm

How soon will an update be out that fixes it?

ajj3085 · Post by **ajj3085** » Wed Jun 20, 2007 5:59 am

Hi,

Ian pointed me here from the CCNET mailing list. Just wanted to post that I'm experiencing this exact problem.

I'll attempt the workaround later today.

feken · Post by **feken** » Mon Jun 25, 2007 6:16 am

Having the same problem here... any workaround besides using 4.0.0?

dankh · Post by **dankh** » Tue Jul 31, 2007 3:07 pm

I upgraded from 3.5 to 4.02 last night, same problem: cc.net would hang at 'checking modifications.'

I installed the 4.0 client on the cc.net server, thinking i would point it to the vault.exe in cc.net, but, after the install of the client, it started running fine.

I am using cc.net v. 1.3.

ian_sg · Post by **ian_sg** » Thu Aug 02, 2007 3:24 pm

The issue was in the client. So yes, installing a non-4.0.1 client on the CCNet machine is the step I'd expect to fix things.