Contents tagged with CruiseControl.NET
-
Vault Login Failed: The server uses a protocol that is not supported by this client.
Installing CruiseControl.NET on a new server and ran into an issue with CruiseControl.NET pulling from the Vault server. I found the following error in the CruiseControl.NET Log:
[PROJECT:ERROR] Vault Standard Login Failed Twice.:The server uses a protocol that is not supported by this client.
Vault Standard Login Failed: The server uses a protocol that is not supported by this client.
The problem turned out to be an incorrect version of the Vault CruiseControl.net Plug-In. I had accidentally grabbed the latest version (7.0) but the Vault server is running an older version of Vault (6.1). The older version could be found on the Previous Vault Downloads page. Installing the correct version of the Vault plugin to match the Vault server solved the problem.
-
CruiseControl.NET Configuration Reference
For some reason it is very difficult for me to find the CruiseControl.NET configuration reference online. Most of the time I end up on an older reference which is out of date and just not correct.
This is the CruiseControl.NET reference that appears to be up-to-date:
CruiseControl.NET Configuration Reference
http://confluence.public.thoughtworks.org/display/CCNET/The+CruiseControl+Configuration+BlockOn the bottom of each page is a list of the children for each configuration block and at the top is the breadcrumb for how far you have drilled down into the tree.
And then you can view the full CruiseControl.NET configuration hierarchy here.
This blog post is mostly for me but also, if I am having a tough time finding the reference then I imagine a lot of other people are too.
-
Prevent CruiseControl.NET error “Source control operation failed: Working copy locked svn”
My CruiseControl.NET build system was running into an error whenever two projects were trying to build at the same time. Both of these projects try to go out to our subversion source control repository and one will win and the other gets locked out.
The build will then fail with this type of error:
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: svn: Working copy 'XXXX' locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) .
To get around this issue you can use the “queue” attribute of the project node:
Here is the Thoughtworks CruiseControl.NET Project configuration reference section: http://confluence.public.thoughtworks.org/display/CCNET/Project+Configuration+Block
Originally I did not set a queue value for each project that is built. The default in this instance is the project name, so each project ends up in its own queue and therefore they will build as soon as possible and cause the locking error.
From the Thoughtworks reference:
queue
The name of the integration queue that this project will use. By default, each project runs in its own queue. (Added in CCNet 1.3)So by setting the queue for each of the projects to the same value (since all of the projects are related), each of them will wait and build one at a time, resolving the “Source control operation failed: svn: Working copy 'XXXX' locked svn” error.
Note: You can also set the queuePriority to indicate the order the project should build when it is in the queue.
This StackOverflow post lead me to this solution: How can I prevent concurrent builds in CruiseControl.NET?
