CruiseControl 1.4 can't connect to Vault 4

[Dudemullet]

Hi i have downloaded and installed both of the softwares successfully but can't seem to integrate them. I have also downloaded sourceforge's dlls to place in the cruise control 'server' folder but I can't seem to connect with ssl disabled, it says that "The server uses a protocol that is not supported by this client"

My config is this

Code: Select all

<sourcecontrol type="vaultplugin" autoGetSource="true" applyLabel="true" cleanCopy="false">
           
            <username>somuser</username>
            <password>somepassword</password>
            <ssl>false</ssl>
	    <host>myhost</host>
            <repository>Initial Repository</repository>
            <folder>$</folder>
            <useWorkingDirectory>true</useWorkingDirectory>
            <workingDirectory>Tester/CCTester/</workingDirectory>
	    </sourcecontrol>

Vault Server Version: 4.0.6.15954
Cruisecontrol Version: version : 1.4.0.3400

[ian_sg]

The vault plugin for CC.NET only works with a Vault 4.1.x server.

If you don't want to upgrade your server, you can use the Vault support that ships with CC.NET, which uses the Vault command-line client and works with Vault 3.0 or newer.

With your 4.0.6 server, you'd need a Vault 4.0.6 client installed on the CC.NET machine (which includes vault.exe, the command-line client). Then you'd change the type attribute on the sourcecontrol node in your configuration from "vaultplugin" to "vault" and add/change other configuration options as described in the documentation.

[Dudemullet]

Thanks ian.

I ended up reverting to the default cruise control plugin I got everything workin now.

Solution:

(short version)
I set the <historyArgs>-rowlimit 0</historyArgs>

(long version)
even when setting the rowlimit to 0 I couldn't connect, because what happens is when you use the parameter history args apparently you forcefully have to use the <repository></repository> value BUT no one tells you this, in fact cruise control sets it up as an optional value here but I found this out after extracting the raw command that was being thrown to the "vault.exe" from the cruise control log. Don't know if this problem emerged after certain release changes or something but I'm also letting them now of this problem, thanks alot for the quick response.

I'm posting my current working connection settings if anyone ever come up with this problem hope it can be useful to somebody.

Code: Select all

<!--
Vault Server Version: 4.0.6.15954
Cruisecontrol Version: version : 1.4.0.3400
-->

   <sourcecontrol type="vault" autoGetSource="true" applyLabel="true">
           <executable>c:\program files\sourcegear\vault client\vault.exe</executable>
           <username>username</username>
           <password>password</password>
           <host>host:port</host>
           <folder>$</folder>
           <ssl>false</ssl>
	   <repository>Initial Repository</repository>
           <useWorkingDirectory>true</useWorkingDirectory>
           <workingDirectory>workingDir</workingDirectory>
	   <historyArgs>-rowlimit 0</historyArgs>
   </sourcecontrol>

[ian_sg]

Thanks Dude!