Setting up your first project

Added by Jon Tirsen, last edited by Aslak Hellesøy on Mar 15, 2005  (view change)

h2 Download and install DamageControl
Follow the instructions on Subversion Access.

h2 (optional) Edit global configuration
Edit the file bin/server.rb in your DamageControl installation directory.

h2 Start server
On Windows: Click the start menu option Start Server.

On Unix or MacOS X:

cd <damagecontrol install directory>
bin/server

h2 Point a browser to the DamageControl admin interface

Start a web-browser and direct it to http://localhost:4712/private/dashboard.

h2 Configure new project

  1. Select New Project.
  2. Project name: Enter project name (must be unique to the server and cannot easily be changed afterwards).
  3. Build command: Enter what command line is used to build the project. It will be executed from the root directory of your checked out project.
  4. Source control: Select your source control system and enter the information used to connect to it. See also [Configuring the SCM connection].
  5. Next build number: You might have already used a number of build numbers ff built your system manually or with some other build tool. In that case enter what build number DamageControl should use for the next successful build.
  6. Hit Save, a Back to project link should now show in the left hand pane.

h2 Trig build!

  1. Click Back to project to return to the project page.
  2. Click Trig build now to start a new build.
  3. DamageControl will now check out your project and execute the build command. Click the tab Console output to monitor progress and any error information that might show up. It is common to do some misstakes when initially configuring a project. If the build doesn't succeed on the first try click Configure and correct the information.
  4. You are done configuring your first project for DamageControll when the first build succeeds!

h2 Next: Installing the DamageControl trigger into your SCM
You will now have to initiate your builds manually every time something is changed. This might be okay but wouldn't it be nice if a build started immediately when someone committed changes to the SCM. To make this possible you need to install the DamageControl trigger into your SCM.

Labels

 
(None)