|You are viewing documentation of TeamCity 5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
In this section:
Integrate with an issue tracker
Dedicated support for YouTrack, Jira, Bugzilla. You can also turn any issue tracker issue ID references in change comments into links. Please see Mapping External Links in Comments for configuration instructions.
Share the build number for builds in a chain build
Suppose you have build configurations A and B that you want to build in sync: use same sources and take the same build number.
Where <btID> is the internal ID of the build configuration C. Please refer to the Build Configuration page for description of how to determine build configuration ID.
More on dependency properties.
We plan to provide more option on build number sharing. Please watch/comment on TW-7745.
Use an external tool that my build relies on
Assume, to run a build you need to use specific external tool to be installed on a build agent. To solve the problem, you have the following options:
Install Multiple Agents on the Same Machine
If you want to install several TeamCity build agents on the same machine, please consider the following:
For installation instructions, refer to Setting up and Running Additional Build Agents.
Change Server Port
See corresponding section in server installation instructions.
Make temporary build files erased between the build
Update your build script to use path stored in
Retrieve Administrator password
On the first start TeamCity displays Administrator Setup page. TeamCity installation should always have a user with System Administrator role in the current authentication scheme.
In rare cases on user authorization scheme switch there can be no System Administrator on the system. In this case you may setup one as follows:
If you forgot Administrator password and use internal database, you can reset the password using the instructions.
Ho do I clear build queue if it got too many builds due to a configuration error
Try pausing the build configuration that has the builds queued. On build configuration pausing all its builds are removed form the queue.
Watch Several TeamCity Servers With Windows Tray Notifier
TeamCity Tray Notifier is used normally to watch builds and receive notifications from a single TeamCity server.
In situations, when you have more than one TeamCity server, and want to monitor them with Windows Tray Notifier simultaneously, you need to start a separate instance of Tray Notifier for each of the servers from the command line with the
See also details in the issue tracker.
Estimate hardware requirements for TeamCity
The hardware requirements differ for the server and the agents.
The agent hardware requirements are basically determined by the builds that are run. Running TeamCity agent software introduces requirement for additional CPU time (but it can usually be neglected comparing to the build process CPU requirements) and additional memory: about 150Mb.
The server hardware requirements depend on the server load. The load on the server depends significantly on the type of the builds and server usage, so here are only some general guidelines.
If you face some Performance issues, they should probably be investigated and addressed individually. e.g. if builds generate too much data, server disk system might need upgrade both by size and speed characteristics.
The load on the server depends on:
Based on our experience, a modest hardware like 3.2 dual core CPU, 3.2Gb memory under Windows, 1Gb network adapter can provide acceptable performance for the setup:
HDD free space requirements are mainly determined by the number of builds stored on the server and the artifacts size/build log size in each.
If the builds generate large number of data (artifacts/build log/test data), using fast hard disk for storing .BuildServer/system directory and fast network between agents and server are recommended.
The general recommendation for deploying large-scale TeamCity installation is to start with a reasonable hardware and add more projects to the server gradually, monitoring the performance characteristics and deciding on necessary hardware or software improvements. Anyway, best administration practices are recommended like keeping adequate disk defragmentation level, etc.
Setup TeamCity in Replication/Clustering Environment
TeamCity does not provide specific support for any of replication/high availability or clustering solutions.
When setting up TeamCity in a replication environment please note that TeamCity uses both database and file storage to save data. You can browse through TeamCity Data Backup and TeamCity Data Directory pages in to get more information on TeamCity data storing.
Basically, both TeamCity data directory on disk and database that TeamCity uses should remain in a consistent state and thus should be replicated together.
Only single TeamCity server instance should use database and data directory at any time.
Move TeamCity projects from one server to another.
Generally, this is not supported. For addressing simple cases manually, please see a comment.
Automatically create or change TeamCity build configuration settings
If you need a level of automation and web administration UI does not suite your needs, there are two possibilities:
Attach Cucumber reporter to Ant build
If you use Cucumber for Java applications testing you should run cucumber with --expand and special --format options. More over you should specify RUBYLIB environment variable pointing on necessary TeamCity Rake Runner ruby scripts:
If you are launching Cucumber tests using Rake build language TC will add all necessary cmdline parameters and env. variables automatically.
Get last successful build number
Use URL like this:
Move TeamCity installation to a new machine
If you need to move existing TeamCity installation to a new hardware or clean OS, you will basically need to:
If server address is changed, you will also need:
Please note that TeamCity Data Directory and database should be used by a single TeamCity instance at any given moment. If you configured new TeamCity instance to use the same data, please ensure you shutdown and disable old TeamCity instance before staring a new one.
After new server start it usually makes sense to check that email, jabber and VCS servers are accessible from the new machine.
A usual advice is not to combine TeamCity update with any environment changes and perform the changes one at a time so that if something goes wrong the cause can be easily tracked.