CruiseControl.net 1.4.4 / Fortress 2.0

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

Moderator: SourceGear

Post Reply
richman32
Posts: 13
Joined: Wed Sep 16, 2009 11:50 am

CruiseControl.net 1.4.4 / Fortress 2.0

Post by richman32 » Wed Sep 16, 2009 1:25 pm

We just upgraded from Fortress 1.1.4 to 2.0.1. Our build servers (CruiseControl.NET 1.4.4 SP1) haven't worked correctly since then.

The build fails with the following exception after all the tasks have completed:
System.NullReferenceException: Object reference not set to an instance of an object.
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressClient.GetVaultClientFolder(String repositoryFolderPath, VaultClientFolder& vcf)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressClient.Label(String repositoryFolderPath, Int64 folderVersion, String label, String labelComment)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressVaultSourceControl.LabelSourceControl(IIntegrationResult result)
at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build(IIntegrationResult result)
at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest request)

As a temporary workaround, the "get" task was modified to apply the label instead of using "applyLabel=true" with the Fortress Client plug-in. The builds now succeed, but the projects are no longer kicking off with the IfModificationExists. We have to manually kick off the builds after each check-in, or set up a scheduled forcebuild task.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: CruiseControl.net 1.4.4 / Fortress 2.0

Post by Beth » Thu Sep 17, 2009 9:09 am

Are there any errors in the Vault server log that correspond to the time the build process fails?
Beth Kieler
SourceGear Technical Support

richman32
Posts: 13
Joined: Wed Sep 16, 2009 11:50 am

Re: CruiseControl.net 1.4.4 / Fortress 2.0

Post by richman32 » Thu Sep 17, 2009 11:23 am

No, there is no corresponding error in the server log.

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

Re: CruiseControl.net 1.4.4 / Fortress 2.0

Post by jeremy_sg » Thu Sep 17, 2009 1:48 pm

During the upgrade, did you switch from the old CLC-based Cruise Control support to the plugin? Would you be willing to mail your ccnet.config file to support at sourcegear dot com?
Subscribe to the Fortress/Vault blog

richman32
Posts: 13
Joined: Wed Sep 16, 2009 11:50 am

Re: CruiseControl.net 1.4.4 / Fortress 2.0

Post by richman32 » Thu Sep 17, 2009 2:49 pm

We did not switch from CLC-based to the plugin during the upgrade. We will email the config.

richman32
Posts: 13
Joined: Wed Sep 16, 2009 11:50 am

Re: CruiseControl.net 1.4.4 / Fortress 2.0

Post by richman32 » Fri Sep 25, 2009 10:25 am

The fix that we implemented was to specify the repository in the ccnet config file. The Fortress 2.0 plug-in apparently does not use the repository specified with rememberlogin even though it is documented to behave that way.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: CruiseControl.net 1.4.4 / Fortress 2.0

Post by Beth » Tue Sep 29, 2009 8:56 am

Thank you for providing the update.
Beth Kieler
SourceGear Technical Support

Post Reply