Monday, April 8, 2013

TeamCity CI Server Default Settings

Just wanted to share with you a quick post and a few screenshots of what the TeamCity CI Server settings will look like after you install it.

I have been using TeamCity CI Server both for personal experiments and also for professional, scalable and highly available client projects. I must say that its performance is quite good, and configuring continuous integration (CI), automated tests runs (AT) and continuous deployment (CD) is straight forward. Also, the user interface and setup steps are way easier than their counterparts on similar solutions like Team Foundation Server, CruiseControl or Jenkins. Also I must say that in my experience TeamCity is better supporting cross-platform solutions.

In the past, I have setup TeamCity on different servers, along custom content management systems and also along third party products like EPiServer (here you can find my EPiServer step-by-step setup article ).

For one of the these setups, I had it serving as the CI server for a team that at its peak had around 10 developers. The CI process was responsible for building and run automated test sets for frontend (flash and .NET) apps, and a scalable .NET backend components like web and RESTful services, email services and web sites. It also served several environments, including Development, Staging and Production, along with several feature branch environments for specific releases.

Anyway, lets take a look at TeamCity’s most important settings.


To access the CI server’s settings, login into TeamCity and click on the Administration link at the top right corner, next to the search box.


In the General tab, you will find the database name and user, the folder paths for the data, artifacts and cache directories, the maximum build artifacts size, and most relevant, the actual server URL, including the port being used.

Following are the version control settings indicating the frequency to check the associated repositories for changes. after that, basic permission flags, including authentication settings and guest user configuration.


The next tab is the Report Tabs, were you can define the custom artifact-based tabs for build reports. In the screenshot you can see Code Coverage and JavaDoc reports configured.

Following are the Issue Tracker and the Agent Cloud tabs, although I haven’t done much with them before.


Next to the right, is the Email Notifier tool, where you can, and should, setup your email notifications. You can also set Jabber notifications by configuring the next tab.

The last tabs are for Plugins, Diagnostics, Tools and Usage Statistics. Their configuration and usage will vary, but they are more of an advanced configuration, rather than the default, more common and simple setup you will usually need.

Again, you can see how simple is to configure the basics to get your CI up and running. Check the screenshots, and feel free to leave your comments or questions on the comments section if you want. Hope this helps!

No comments:

Post a Comment