Cruise Control .NET Resources

0 comments suggest edit

Since I’m just getting started with Cruise Control, I thought I’d look around the web and blogosphere and put together some resources on configuring CruiseControl.NET.

And there’s also the CruiseControl.NET site itself and the community site.

After reading through many of these resources, I have a question about directory structures. You see, I try to be an obedient Microsoft developer (will it pay off?) and set up my directories as outlined in the Microsoft Patterns & Practices article Team Development with Visual Studio .NET and Visual SourceSafe.

The article proposes that you group code into “Systems” which may contain one or more VS.NET Solutions. A Solution of course may contain one or more Projects. Below is figure 3.5 from the article illustrating the directory structure.

Directory Structure \ Figure 3.5. Visual Studio .NET and VSS Folder Structure

In general, projects and solutions won’t be shared across systems, i.e. a solution in one system won’t reference a project in another. However I do have one exception in that I have a code library system with projects that other solutions may reference. For example:

Projects
    CodeLibrarySystem
        CodeLibrarySolution
            Project1
            Project2

    SomeOtherSystem
        SomeSolution
            Project1
            Project3

So, in my case, should I map a CruiseControl.NET project to a System or a Solution? Any recommendations?

Found a typo or error? Suggest an edit! If accepted, your contribution is listed automatically here.

Comments

avatar

5 responses

  1. Avatar for Craig
    Craig August 17th, 2004

    I responded to your comment somewhat on my blog, but realize I didn't answer your question directly.



    Either Project1 is evolving with one system, the other, neither, or everything evolves together.



    If it evolves with one or the other system, then build it with that system and periodically update the *binary* into the other system, so its interface stays relatively stable.



    If it evovles independently, build it separately, and manually update it periodically into both the other systems.



    If everything evolves together, then you can either build both systems separately, or build everything all together at once.



    The thing you don't want to do is to link systems closely together where minute-to-minute changes can break systems where the teams building the two pieces don't have a shared strategy. That just leads to you showing up in the morning and finding out that the interface of Project1 is now completely different.

  2. Avatar for Igor
    Igor December 7th, 2004

    Hi All,



    I cannot find CruiseControl.net Version 0.7. The WebSite http://ccnet.thoughtworks.com is down or inaccessible. Maybe somebody can e-mail me?

    Thanks in advance



    sdorovo@hotmail.com

  3. Avatar for James
    James July 24th, 2007

    I'm attempting to get Crusie Control.NET working with SQLUNit which uses ant as the builder. Using the confluence Wiki I am able to see the ant output in the Crusie Control web page but not the results of the test itself. Any recommendations on how to make this work or some sites that show how this is accomplished?
    Hopefully this request is ok in this space. By the way I am unable to access the ccnet.thoughtworks site too
    Thanks in advance
    James

  4. Avatar for srinath
    srinath November 14th, 2007

    Hi, it is real good aricle about cruise control for starters. I hav one doubt..How to Configure cruise control for using NAnt for automated builds of .net projects.

  5. Avatar for Shefali Agrawal
    Shefali Agrawal February 19th, 2008

    Hi,
    I have implemented cruise control for my .net project.We are using VSS as configuration managment tool.Project size is very large.I want to implement Nant or something else for getting all the modified files from VSS.Kindly,let me know.
    Thanks