Build State
The build state icon appears next to each build under the expanded view of the build configuration on the Projects page.
Build States
Icon | State | Description |
|---|---|---|
| running successfully | A build is running successfully. |
| successful | A build finished successfully in all specified build configurations. |
| running and failing | A build is failing. |
| failed | A build failed at least in one specified build configuration. |
| cancelled | A build was cancelled. |
Canceled/Stopped build
Stopping a running build results in the build status displayed as cancelled. You can stop a running build from the Working with Build Results, Viewing Build Configuration Details or using the Stop option from the Actions drop-down.
When a build is started, the build process calls the runner process and listens to its output. The stop command kills the runner process, then the build process stops.
Personal Build States
Icon | State | Description |
|---|---|---|
| running successfully | A personal build is running successfully. |
| successful | A personal build has completed successfully for all specified build configurations. |
| running and failing | A personal build is running with errors. |
| failed | A personal build failed at least in one specified build configuration. |
Hanging and Outdated Builds
TeamCity considers a build as hanging when its run time significantly exceeds estimated average run time and the build did not send any messages since the estimation exceeded. A running build can be marked as Outdated if there is a build which contains more changes but it is already finished. Hanging and outdated builds appear with the icon 
. Move the cursor over the icon to view a tooltip that displays additional information about the warning.
Failed to Start Builds
Builds which did not get to the point to launch the first build step are called "failed to start" and are marked with the icon 
. This often is an indication of a configuration error and should usually be addressed by a build engineer rather then a developer if there such roles separation. For example, VCS repository can be down when build starts, or artifact dependencies can't be resolved, and so on. In case such error occurs, TeamCity:
doesn't send build failed notification (unless you have subscribed to "the build fails to start" notification)
doesn't associate pending changes with this build, i.e. the changes will remain pending, because they were not actually tested
doesn't show such build as the last finished build on the overview page
such builds will not affect build configuration status and status of developer changes
shows "configuration error" stripe for build configuration with such a build