Cruise Control.Net with Vault Pro 5.1

[mtidd]

The new Vault Pro 5.1 (Fortress) release does not include the cruisecontrol.net plugin on the download page.

Will the cruisecontrol.net plugin from Fortress 2 work with the new release?

[Beth]

Currently, you don't have to change anything about your CCNET plugin. The previous CCNET plugin should continue working as is. We will be posting the CCNET plugin for Vault Pro 5.1 in a few days.

[jclausius]

mtidd,

The Vault Professional's download page has been updated with the release for Vault Professional. Please see the ReadMe.txt file within the download for changes to control blocks for <vaultpro> and <workitemcomment> as well as updated installation instructions.

[richman32]

Trying to use the Vault Pro 5.1 plugin with cruise control and getting the following in the ccnet.log file when attempting to start the ccservice:

2010-11-19 16:20:53,436 [4:DEBUG] The trace level is currently set to debug. This will cause CCNet to log at the most verbose level, which is useful for setting up or debugging the server. Once your server is running smoothly, we recommend changing this setting in C:\Program Files\CruiseControl.NET\server\ccservice.exe.Config to a lower level.
2010-11-19 16:20:53,452 [4:INFO] CruiseControl.NET Server 1.5.7256.1 -- .NET Continuous Integration Server
2010-11-19 16:20:53,452 [4:INFO] Copyright © 2003 - 2010 ThoughtWorks Inc. All Rights Reserved.
2010-11-19 16:20:53,452 [4:INFO] .NET Runtime Version: 2.0.50727.3607 Image Runtime Version: v2.0.50727
2010-11-19 16:20:53,452 [4:INFO] OS Version: Microsoft Windows NT 5.1.2600 Service Pack 3 Server locale: English (United States)
2010-11-19 16:20:53,452 [4:INFO] Reason: SCM start
2010-11-19 16:20:54,139 [4:ERROR] A fatal error occurred while starting the CruiseControl.NET server
2010-11-19 16:20:54,327 [4:ERROR] INTERNAL ERROR: Multiple types exist with the same ReflectorTypeAttribute name "workitemcomment": (ThoughtWorks.CruiseControl.Core.Publishers.VaultProItemCommentPublisher, ThoughtWorks.CruiseControl.Core.Publishers.VaultProItemCommentPublisher)
----------
Exortech.NetReflector.NetReflectorException: Multiple types exist with the same ReflectorTypeAttribute name "workitemcomment": (ThoughtWorks.CruiseControl.Core.Publishers.VaultProItemCommentPublisher, ThoughtWorks.CruiseControl.Core.Publishers.VaultProItemCommentPublisher)
at Exortech.NetReflector.NetReflectorTypeTable.Add(Type type)
at Exortech.NetReflector.NetReflectorTypeTable.Add(Assembly assembly)
at Exortech.NetReflector.NetReflectorTypeTable.Add(String assemblyFilename)
at Exortech.NetReflector.NetReflectorTypeTable.Add(String path, String searchPattern)
at ThoughtWorks.CruiseControl.Core.Config.NetReflectorConfigurationReader..ctor()
at ThoughtWorks.CruiseControl.Core.CruiseServerFactory.NewConfigurationService(String configFile)
at ThoughtWorks.CruiseControl.Core.CruiseServerFactory.CreateLocal(String configFile)
at ThoughtWorks.CruiseControl.Core.CruiseServerFactory.CreateRemote(String configFile)
at ThoughtWorks.CruiseControl.Core.CruiseServerFactory.Create(Boolean remote, String configFile)
at ThoughtWorks.CruiseControl.Service.AppRunner.CreateAndStartCruiseServer()
at ThoughtWorks.CruiseControl.Service.AppRunner.Run(String action, Boolean usesShadowCopying)
----------

Any ideas what might be wrong?

[richman32]

I was actually able to figure out the problem. I somehow got two different versions of the plugin dll in the CruiseControl.NET\server folder (ccnet.vaultpro.plugin.dll and ccnet.vaultprovault.plugin.dll). Once I deleted the one that shouldn't have been there (ccnet.vaultprovault.plugin.dll), everything worked fine.

[Beth]

Thank you for the update. I'm happy to hear you are working now.

[jclausius]

Someone may have accidentally installed the original Vault Standard 5.1 plugin by mistake (as there was a compatibility issue Vault 5.1 Professional did not have a CC.Net release).

In any case, with the upcoming maintenance release of Vault 5.1.1 (and subsequent releases) there are now two files:
a) Vault Professional will use ccnet.vaultpro.plugin.dll
b) Vault Standard will use ccnet.vault.plugin.dll