Vault 4.1.4 and CCNET 1.0.0.1062
Moderator: SourceGear
Vault 4.1.4 and CCNET 1.0.0.1062
We are upgrading to Vault 4.1.4 and I am testing its compatibility with CCNET 1.0.0.1062.
1) I just installed the Vault 4.1.4 client on the CCNET server.
2) I use RememberLogin on the CCNET server
3) CCNET.config sourcecontrol entries below:
<sourcecontrol type="vault">
<executable>d:\program files\sourcegear\vault client\vault.exe</executable>
<folder>$/System/Service/AddressServices/V01</folder>
<historyArgs>-rowlimit 2000</historyArgs>
<ssl>false</ssl>
</sourcecontrol>
4) When CCNET tries to connect to Vault, the following error is generated:
<vault>
<error>
<exception>VaultClientIntegrationLib.UsageException: Please specify -user, -password, and -host.
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
at VaultClientIntegrationLib.ServerOperations.Login()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>
</vault>
Would appreciate suggestions on resolution. Thanks
1) I just installed the Vault 4.1.4 client on the CCNET server.
2) I use RememberLogin on the CCNET server
3) CCNET.config sourcecontrol entries below:
<sourcecontrol type="vault">
<executable>d:\program files\sourcegear\vault client\vault.exe</executable>
<folder>$/System/Service/AddressServices/V01</folder>
<historyArgs>-rowlimit 2000</historyArgs>
<ssl>false</ssl>
</sourcecontrol>
4) When CCNET tries to connect to Vault, the following error is generated:
<vault>
<error>
<exception>VaultClientIntegrationLib.UsageException: Please specify -user, -password, and -host.
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
at VaultClientIntegrationLib.ServerOperations.Login()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>
</vault>
Would appreciate suggestions on resolution. Thanks
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Look in the zip file of the Vault Cruise Contol Plugin for the readme.txt. It will have more details about the plugin and a good example.
<sourcecontrol type="vaultplugin" autoGetSource="true" applyLabel="true" cleanCopy="false">
<username>my_username</username>
<password>my_password</password>
<host>my_buildserver</host>
<repository>my_repository</repository>
<folder>$</folder>
<ssl>true</ssl>
<useWorkingDirectory>true</useWorkingDirectory>
<workingDirectory>project/src</workingDirectory>
</sourcecontrol>
<sourcecontrol type="vaultplugin" autoGetSource="true" applyLabel="true" cleanCopy="false">
<username>my_username</username>
<password>my_password</password>
<host>my_buildserver</host>
<repository>my_repository</repository>
<folder>$</folder>
<ssl>true</ssl>
<useWorkingDirectory>true</useWorkingDirectory>
<workingDirectory>project/src</workingDirectory>
</sourcecontrol>
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Thanks Beth.
1. Our current ccnet.config production entries are below. We are currently at Vault 3.5.1. Rememberlogin now works in production:
<sourcecontrol type="vault">
<executable>c:\program files\sourcegear\vault client\vault.exe</executable>
<historyArgs>-rowlimit 10</historyArgs>
<folder>$/Script/Build/Deploy</folder>
<ssl>false</ssl>
</sourcecontrol>
2. In dev, I upgraded Vault to 4.1.4. Setting RememberLogin and leaving ccnet.config settings same as above (1) one causes Vault login errors. If I set sourcecontroltype to include credentials:
<sourcecontrol type="vault">
<executable>d:\program files\sourcegear\vault client\vault.exe</executable>
<username>builder</username>
<password>mypassword</password>
<host>uslaxdevapp01</host>
<repository>griffin</repository>
<historyArgs>-rowlimit 10</historyArgs>
<folder>$/Script/Build/Deploy</folder>
<ssl>false</ssl>
</sourcecontrol>
--> CCNET works. However, I prefer to use RememberLogin.
3. Next I configure CCNET to use the Vault plugin by downloading the components and updating ccnet.config as follows:
<sourcecontrol type="vaultplugin" autoGetSource="true" applyLabel="true" cleanCopy="false">
<executable>d:\program files\sourcegear\vault client\vault.exe</executable>
<username>builder</username>
<password>mypassword</password>
<host>uslaxdevapp01</host>
<repository>griffin</repository>
<historyArgs>-rowlimit 10</historyArgs>
<folder>$/Script/Build/Deploy</folder>
<ssl>false</ssl>
</sourcecontrol>
--> Now the CCNET service fails to start with the following error:
Service cannot be started. System.BadImageFormatException: The format of the file 'ccnet.fortressvault.plugin.dll' is invalid.
File name: "ccnet.fortressvault.plugin.dll"
1. Our current ccnet.config production entries are below. We are currently at Vault 3.5.1. Rememberlogin now works in production:
<sourcecontrol type="vault">
<executable>c:\program files\sourcegear\vault client\vault.exe</executable>
<historyArgs>-rowlimit 10</historyArgs>
<folder>$/Script/Build/Deploy</folder>
<ssl>false</ssl>
</sourcecontrol>
2. In dev, I upgraded Vault to 4.1.4. Setting RememberLogin and leaving ccnet.config settings same as above (1) one causes Vault login errors. If I set sourcecontroltype to include credentials:
<sourcecontrol type="vault">
<executable>d:\program files\sourcegear\vault client\vault.exe</executable>
<username>builder</username>
<password>mypassword</password>
<host>uslaxdevapp01</host>
<repository>griffin</repository>
<historyArgs>-rowlimit 10</historyArgs>
<folder>$/Script/Build/Deploy</folder>
<ssl>false</ssl>
</sourcecontrol>
--> CCNET works. However, I prefer to use RememberLogin.
3. Next I configure CCNET to use the Vault plugin by downloading the components and updating ccnet.config as follows:
<sourcecontrol type="vaultplugin" autoGetSource="true" applyLabel="true" cleanCopy="false">
<executable>d:\program files\sourcegear\vault client\vault.exe</executable>
<username>builder</username>
<password>mypassword</password>
<host>uslaxdevapp01</host>
<repository>griffin</repository>
<historyArgs>-rowlimit 10</historyArgs>
<folder>$/Script/Build/Deploy</folder>
<ssl>false</ssl>
</sourcecontrol>
--> Now the CCNET service fails to start with the following error:
Service cannot be started. System.BadImageFormatException: The format of the file 'ccnet.fortressvault.plugin.dll' is invalid.
File name: "ccnet.fortressvault.plugin.dll"
Re: Vault 4.1.4 and CCNET 1.0.0.1062
1) How do you have your rememberlogin written? Can you post that and just x out important information?
What happens if you try to use rememberlogin with just the command line and then try a few manual Vault commands on the command line?
3) Do you have the 2.0 .NET framework installed on that machine? The latest version requires the 2.0 .NET framework.
What happens if you try to use rememberlogin with just the command line and then try a few manual Vault commands on the command line?
3) Do you have the 2.0 .NET framework installed on that machine? The latest version requires the 2.0 .NET framework.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Thanks.
1. "d:\Program Files\SourceGear\Vault Client\vault.exe" REMEMBERLOGIN -user builder -password XXXXXX -repository griffin -host uslapXXXXXXX
It runs successfully, resulting in a return value of true
Running Vault commands from the commands line after RemeberLogin works
2. Yes, Framework 2.0 is installed on the machine.
1. "d:\Program Files\SourceGear\Vault Client\vault.exe" REMEMBERLOGIN -user builder -password XXXXXX -repository griffin -host uslapXXXXXXX
It runs successfully, resulting in a return value of true
Running Vault commands from the commands line after RemeberLogin works
2. Yes, Framework 2.0 is installed on the machine.
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Do you hve a Vault GUI client on that machine? If so, does that function correctly?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Yes its installed and works properly.
Re: Vault 4.1.4 and CCNET 1.0.0.1062
I think your version of CCNET doesn't support the 2.0 .NET framework. You should upgrade Cruise Control to a version that does support the 2.0 .NET framework.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Thanks. Will try an upgrade from here and provide feedback later.
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Have you had any results yet from an upgrade?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 4.1.4 and CCNET 1.0.0.1062
Holding off on CCNET upgrade until after the Vault upgrade this month. Just did some workarounds on the CCNET side for now. Thanks
Re: Vault 4.1.4 and CCNET 1.0.0.1062
One additional thing that could be causing what you are seeing....
Is it possible that you ran the rememberlogin command under a Windows user account that is different from the Windows account that CC.Net uses?
Is it possible that you ran the rememberlogin command under a Windows user account that is different from the Windows account that CC.Net uses?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support