Hi, We have the same configuration than yours. Contrary to what Ruben says, it is possible to set a CCNet server with this configuration but it demands some work and customization of CCNet.
Here is the queue on the server: CCNet |-- Source control project |-- Solution A project |-- Solution B project |-- ..... So first you need to have a project only for SourceControl operations. This project will have the max priority queue. It has a task which scans the result of the source control block execution and returns 0 (success) if a modification has been found of 1 (failure) if no modification has been found. To be able to scan this result in the .state file, you need to add a new XML element stored in it, I called it "HasModification", it is written right after the source control block execution and before the task block execution, this way the scan task can effectively returns 0 or 1 based on the "HasModification" value. On task failure the source control project must cancel the pending projects. To do this I wrote a little plugin which works like the force build publisher but instead it removes a specific project from the queue. You can find this plugin here: http://jira.public.thoughtworks.org/browse/CCNET-1271 If the task succeed then it let the Solution projects in the queue do their jobs. Secondly, you need to order you solution projects based on their dependencies, to do this, you just have to use the queue priority, here is how it works: 0 = the project is added at the end of the queue then 1 is the max priority so we have 1 > n > 0 To conclude, you need a last trigger project which will launch all the projects with a force build publisher task. This project will have a queue priority set to 0. I hope this would help. My first advice is to get my CancelPending plugin which will open to you a bunch of new design possibilities with CCNet. Sylvain On 29 jan, 12:10, Victor <[email protected]> wrote: > I'm a complete newbie in setting up CCNet, just used CC it as > developer till now. > > I have a list of dependent MSVS2005 solution files, which till now > were build using a simple batch file. > > Most hints I read in CCNet/VisualStudio context assumed either single > or independent solutions. > > Any initial suggestions or links how to set-up this optimally?
