Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 344901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T11:02:01+00:00 2026-05-12T11:02:01+00:00

CruiseControl.net creates (by default) for each project a subdirectory under: c:\Program File\CruiseControl.NET\server How can

  • 0

CruiseControl.net creates (by default) for each project a subdirectory under: c:\Program File\CruiseControl.NET\server

How can I change that? (it’s such a bad idea to mix data with program files…)

I found a way to configure the artifacts directory per project, but that’s not quite it (it’s merely a subdirectory of the project directory).

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T11:02:01+00:00Added an answer on May 12, 2026 at 11:02 am

    I have CC.NEt not installed here, and I have atm no access to my build-server at work, but if I remember well, you should find 2 configuration files in your c:\Program Files\CruiseControl.NET folder.

    ccnet.exe.config and ccservice.exe.config.

    The first configuration file is used when you run CC.NET using the console app, the second one is used when you start CC.NET as a service.

    In those files, you should find a configuration-setting which points to the location where the configuration-file(s) that describe the build-process for your projects can be found.

    edit:
    In the ccservice.exe.config file, you’ll find a key in the appSettings section which is called ccnet.config. Change the value of this key to the path where you want to put the ccnet.config file.
    If this key is not present, you can add it:

    <appSettings>
        <!-- Without this appSetting ccservice will look for ccnet.config in its own directory. -->
        <add key="ccnet.config" value="D:\CCNetConfigFiles\ccnet.config"/>
    </appSettings>
    

    This is how I’ve done it:

    • I’ve changed the ccnet.config appSetting in the ccservice.exe.config file, so that CruiseControl.NET searches for the ccnet.config file in a different location instead of the standard location. (As described above). (I understand that you do not want to do this ?)
    • I’ve changed the ccnet.config file itself, so that it looks like this:
    <!DOCTYPE cruisecontrol [
        <!ENTITY project1        SYSTEM "file:D:\CCNETConfigFiles\project1\project1buildconfig.xml.config">
        <!ENTITY project2        SYSTEM "file:D:\CCNETConfigFiles\project2\project2buildconfig.xml.config">
        <!ENTITY project3    SYSTEM "file:D:\CCNETConfigFiles\project3\project3buildconfig.xml.config">
    ]>
    <cruisecontrol>
    
      &project1;
      &project2;
      &project3;
    
    </cruisecontrol>
    

    By doing this, I can have each project configuration in its own file, and I can put each project-configuration in its own directory.

    • Then, I just have to make sure that in each project config-file, I remove the cruisecontrol tags, because otherwise the ccnet.config file wouldn’t validate against the schema.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've got a problem with CruiseControl .Net (version 1.4.3.4023) in that when the server
I have set up cruisecontrol.net cs for my project that has a number of
Is there any cruisecontrol.net extension, that monitor the event when the config file modified,
I have a project in CruiseControl.net that I am trying to create a schedule
We have a CruiseControl.NET Server 1.5.0.4401 running. One project uses an external compiler, which
We have tests using WatiN that we want to run on our CruiseControl.NET server.
In CruiseControl.NET there appears to be the same xsl stylesheets in the server directory
When I launch CruiseControl.NET with a particular configuration file I receive the following error:
I have CruiseControl.NET Version 1.4 set up on my development server. Whenever a developer
I have downloaded cruisecontrol.net setup and have installed it in C:\Program Files\CruiseControl.NET . It

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.