We updates the CruiseControl.NET website to the latest version of Chiliproject.

A lot of bugs were fixed and we also got the new more usable design.

I hope you'll enjoy it.

There are now pages that cover in detail on how setting up CCNet for different scenario's : CI server, no security, bolted down security, gathering statistics, staging, ...

This will show how you can setup CCNet, and these pages guide you through it, step by step.
Setting up CCNet.config, making a build script, ...

This will help first time users a lot, and maybe give others some alternatives or tips :-)

• Build Server Scenarios
  • Step 1 Setting up Source Control
  • Step 2 Build on Check-in
  • Step 3 Add unit tests
  • Step 4 Add Coverage
  • Step 5 Add source code analysis
• Security scenarios
  • Scenario 1 Small In-house Development Team
  • Scenario 2 Large In-house Development Team
  • Scenario 3 Open Source Project

Other pages coming in the near future

Tips and hints are welcome ...

CCNet is now converted to VS2010. We will still target the 3.5 framework for the moment.
The conversion allows us to use the benefits of VS2010, what also should help the devs, finding people with VS2008 (not express) is becoming more difficult.

Docs are uploaded, except for the security plugins. I need to check these further, since the existing docs do not explain that much.
As before, if something is missing, bad, inform us so we can fix it.

All the docs for configuring the CCNet service are ported to the new site. This is the bulk of the documentation, a lot of this is generated, but creating the structure, and making the pages took a lot more time than I imagined. Hopefully the docs for Dashboard and CCTRay will be a lot easier.
The doc generator and uploader are also updated, meaning keeping this documentation up-to-date will be a piece of cake.

When those docs are done, we can concentrate on user stories, special conditions and the like.

Should any one find missing, bad layout, inform us so we can correct the docs.

After years of good collaboration with Thoughtworks, it appeared that Thoughtworks had less resources to spent for CCNet.
This problem came painfully visible when their site was hacked with a virus. It took a long time for the help page to come back up, and the build server is still not up.

Some months ago we (the active members) decided to move the hosting to another server, so we would be less dependent on Thoughtworks. No hard feelings, it were great years of cooperation but time moved on.

The reason it took a few months to set everything up was due to lack of time of us. Communication could have been better, but we're all doing this (maintaining CCNet) in our own free time, without getting paid. Hopefully this downtime will not happen again.

The license of CCNet is still the same as it was before the move, we just moved the build server and the documentation site, everything else stays the same till further notice :-)

• we can update / alter the site at any time.
• there is 1 site for the wiki, bug reports and forum (before there was Jira and Confluence, no forum) meaning 1 user and password
• a Linux build server is also up and running, meaning more Mono compatibility.
• moved from svn to Git, which should make it a lot easier for people to contribute.
• Chili has some options that Jira did not have : Calendar, Gantt chart, ....

Now lets get CCNet back in the picture, stay tuned for more news.