CruiseControl.net doesn't work with 3.5

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

Moderator: SourceGear

Post Reply
brydon
Posts: 18
Joined: Mon Apr 18, 2005 9:15 am

CruiseControl.net doesn't work with 3.5

Post by brydon » Mon Aug 14, 2006 11:41 am

We recently upgraded our Vault server to 3.5 and now our nightly builds are broken. I've upgraded the vault client on the build machine and I'm able to launch the client and connect to the vault server.

The error we're seeing is below. Any hints on how to proceed or what to try next??




System.Web.Services.Protocols.SoapException: 1021 : FailServiceVersionNotSupport
ed
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClie
ntMessage message, WebResponse response, Stream responseStream, Boolean asyncCal
l)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodN
ame, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Int32
[] clientSupportedVersions)
at VaultClientNetLib.VaultConnection.Login(String strURLBase, String strUsern
ame, String strPassword)
at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String usern
ame, String password)

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Aug 14, 2006 12:11 pm

Can you check CruiseControl's setup for the Vault command line client? Verify it is pointing to the correct version of Vault.

Also, check that the CC.Net connection is hitting a Vault 3.5 server.
Jeff Clausius
SourceGear

brydon
Posts: 18
Joined: Mon Apr 18, 2005 9:15 am

NAnt issue

Post by brydon » Mon Aug 14, 2006 1:23 pm

At this point, I'm assuming this is technically a NAnt to Vault issue as simply running our NAnt task directly results in the same error. It's obviously failing on our task where we get the recent source from vault.

So having said that I'm still not sure what to try.

brydon
Posts: 18
Joined: Mon Apr 18, 2005 9:15 am

ccnet.config

Post by brydon » Mon Aug 14, 2006 1:25 pm

sorry, but to answer your question, I think ccnet's pointing to the correct spot...

<sourcecontrol type="vault" autoGetSource="false" applyLabel="false">
<executable>c:\program files\sourcegear\vault client\vault.exe</executable>

brydon
Posts: 18
Joined: Mon Apr 18, 2005 9:15 am

Vault command line

Post by brydon » Mon Aug 14, 2006 1:29 pm

As well, I am able to run command line connects from that server...

The following command returns valid results....

C:\Program Files\SourceGear\Vault Client>vault listusers -user brydon -host 64.34.162.212 -password ****

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Mon Aug 14, 2006 1:29 pm

NAnt tasks are specific to a particular version of Vault, so you need to make sure you're using the 3.5 NAnt tasks, which can be downloaded here: http://www.sourcegear.com/vault/downloads.html. Note that your NAnt script explicitly loads the tasks so you need to check that you're loading the right dll.

I understand that this probably doesn't apply to you, but for others who stumble upon this thread: CruiseControl.NET definitely does work with Vault 3.5. CC.NET interacts with Vault via the command-line client. As long as you have your ccnet.config set up to use the 3.5 vault.exe and hit a 3.5 server, everything should work as it did under 3.1.
Ian Olsen
SourceGear

brydon
Posts: 18
Joined: Mon Apr 18, 2005 9:15 am

Post by brydon » Mon Aug 14, 2006 1:50 pm

Sorry, I just realized that the title of my post was poorly worded and misleading....

I didn't realize that the tasks were tied to a release. I'm pretty sure that's the issue then. Thanks a lot for the help and apologies if the title causes any confusion.

Post Reply