Geeks With Blogs

Rob Reynolds

Subscribe to Fervent Coder RSS
Subscribe to Fervent Coder by Email

About Me

I manage several open source projects. Need...
   ...package management for Windows?
   ...automated builds?
   ...database change management (migrations)?
   ...your application to check email?
   ...a monitoring utility?

I also write for

Like what you are reading? Want to buy me a cup of coffee?
PayPal - The safer, easier way to pay online!

Fervent Coder Coding Towards Rob Reynolds


Last time we created a project. This time we will set up the build configuration with it.


Create a Build Configuration

1. Click {add a build configuration} for this project.


2. In the [Name:] field, we need to add something descriptive. We are building the trunk on every change. Let’s call it Bombali Trunk CI.


3. In [Artifact paths:] enter code_drop/*.zip.


4. In the Fail build if: section, ensure that these settings are checked:

    a. build process exit code is not zero

    b. at least one test failed

    c. an out of memory or crash is detected


5. In the Build options: section, ensure that these settings are checked:

    a. Enable hanging builds detection


6. Click {VCS settings >>}.


7. Click on {Create and attach new VCS root}.


8. Enter a name in [VCS root name:]. We are going to use our project and where the source is from, so we put in Bombali SVN. Choose what is most appropriate for you.


9. Select the appropriate source control. We select Subversion as our source control. NOTE: Each source control option has different options. We are only going to talk about SVN.


10. We enter the [URL:] to our project.


11. The next option is [Externals support:]. If you use externals at all, you would want to enable full support. And you would know if you are using externals. Otherwise, leave default to ignore externals.


12. I like to clear out [Labeling rules], but that is a matter of preference. With UppercuT we can get back to any specific build and revision based on our DLLs. Choose what is most appropriate for you.


13. I leave the [Checking interval:] at the default of [use global server setting (60 seconds)]. Choose what is most appropriate for you.


14. Click {Test connection}. If it is successful, we can move on. If not, make the edits you need.


15. Click {close}.


16. Click {Save} to continue.


17. In the Checkout Settings section:

    a. [VCS checkout mode:] is Automatically on server.

    b. [Checkout directory:] is an appropriate directory for you. We are going to use C:\CodeBuild\Bombali.

    c. We leave [Clean all files before build:] unchecked. Choose what is most appropriate for you.


18. In the VCS Labeling section:

    a. We select [Do not label]. Choose what is most appropriate for you.


19. Click on {Choose Build Runner >>}.


20. Set [Build runner:] to Command Line.

21. Set [Command executable:] to zip.bat.


22. We are leaving the XML Report Processing section set to its default for now. Choose appropriately if you would like to use this section.

23. Click {Save}.


24. You should get a message that the build configuration has been created successfully.


25. Click on [Build triggering].


26. Check [Enable triggering when files are checked into VCS].


27. Click {Save}.


28. Set any other options you need to set.


Next time we are going to run the build.

 UppercuT - TeamCity Integration Series

  1. Part 0 - Prerequisites
  2. Part 1 - Set up TeamCity Project
  3. Part 2 - Build Configuration
  4. Part 3 - Run the Build
  5. Part 4 - Code Drop / Artifacts

With this knowledge you shall build.

kick it on Posted on Monday, June 8, 2009 6:52 AM Code , UppercuT | Back to top

Comments on this post: UppercuT - TeamCity Integration - Part 2 (Create a Build Configuration)

Comments are closed.
Comments have been closed on this topic.
Copyright © Robz / Fervent Coder | Powered by: | Join free