|You are viewing documentation of TeamCity 7.x, which is not the most recently released version of TeamCity. Please refer to the listing to choose another version.|
When creating a build configuration, on the first page of the wizard specify the following options:
Use these fields to provide the name for the build configuration and optional description. Note that the Name field should not contain special characters.
In the Build number format field you can specify a pattern which is resolved and assigned to the Build Number on the build start.
The following substitutions are supported in the pattern:
Though not required, it is still highly recommended to ensure the build numbers are unique. Please include build counter in the build number and do not reset the build counter to lesser values.
Use the Build counter field to specify the counter to be used in the build numbering. Each build increases the build counter by 1. Use the Reset counter link to reset counter value to 1.
To learn what is called a build artifact in TeamCity, please refer to the Build Artifact concept page. On the General Settings page of the build configuration you can specify artifacts of a build using comma-, or newline- separated values of the format:
The format contains:
The source names can be paths relative to the build checkout directory or absolute paths. The usage of absolute paths is discouraged, please try to use path relative to the build checkout directory.
An optional part starting with => symbols and followed by the target directory name can be used to publish the files into the specified target directory. If target directory is omitted the files are published in the root of the build artifacts. You can use "." (dot) as reference to the build checkout directory.
You can use build parameters in the artifacts specification. For example, use "mylib-%system.build.number%.zip" to refer to a file with the build number in the name.
Specify additional options for the builds of this build configuration.
Select the Enable hanging build detection option to detect probably "hanging" builds. A build is considered to be "hanging" if its run time significantly exceeds estimated average run time and the build did not send any messages since the estimation exceeded. To properly detect hanging builds TeamCity has to estimate the average time builds run based on several builds. Thus if you have a new build configuration, it may make sense to enable this feature after a couple of builds have run, so that TeamCity will have enough information to estimate the average run time.
This option enables retrieving the status and basic details of the last build in the build configuration without requiring any user authentication.
The status can be retrieved via the HTML status widget described below, or via single icon with the help of REST API.
This feature allows you to get an overview of the current project status on your company's website, wiki, Confluence or any other web page.
When the feature is enabled, you need to include the following snippets of code in the web page source:
To provide up-to-date status information on specific build configurations, use the following parameter in the URL as many times as needed:
It is also possible to show the status of all a project's build configurations by replacing "&buildTypeId=<buildConfigurationId>" with "&projectId=<projectId>". You can select a combination of these parameters to display the needed projects and build configurations on your web page.
You can also download and customize the externalStatus.css file (for example, you can disable some columns by using display: none; See comments in externalStatus.css). But in this case, you must not include the withCss=true parameter, but provide the CSS styles explicitly, preferably in the <head> section, instead.
Enabling the status widget also allows non-logged in users to get RSS feed for the build configuration.
Specify the number of builds of the same configuration that can run simultaneously on all agents. This option helps avoid the situation, when all of the agents are busy with the builds of a single project. Enter 0 to allow an unlimited number of builds to run simultaneously.