TeamCity
 
You are viewing the documentation for an earlier version of TeamCity.

Build State

Last modified: 20 April 2023

The build state icon appears next to each build under the expanded view of the build configuration on the Projects page.

Build States



Personal Build States



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 Outdated build. Move the cursor over the icon to view a tooltip that displays additional information about the warning.

Failed to Start Builds



Builds failed to start due to a configuration error are marked with the icon Failed to start. 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