|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
You can turn 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
See instructions at Setting up and Running Additional Build Agents.
Change Server Port
To change the server's port, in the
To apply changes, you should restart server.
Make temporary build files erased between the build
Update your build script to use path stored in
Force creating System Administrator account
Since TeamCity 4.5
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.
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.
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 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.