You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.x documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

Skip to end of metadata
Go to start of metadata

A History Build is a build that starts after a build with more recent changes. That is, a history build is a build that disrupts normal builds flow according to the order of the source revisions.

A build may become a history build in the following situations:

  • If you initiate a build on particular changes manually using the Run Custom Build dialog.
  • If you have a VCS trigger with a quiet period set. During this quiet period a different user can start a build with more recent changes. In this case, your automatically triggered build will have an older source revision when it starts, and will be marked as a history build.
  • If there are several builds of the same configuration in the build queue and they have fixed revisions (e.g. they are part of a Build Chain). If someone manually re-orders these builds, the build with fewer changes can be started first.

As the history build does not reflect the current state of the sources, the following restrictions apply to its processing:

  • The status of a history build does not affect the project/build configuration status.
  • A user does not get notifications about history builds unless they subscribed to notifications on all builds in the build configuration.
  • History builds are not shown on the Projects or Build Configuration > Overview page as the last finished build of a configuration.
  • The Investigation option is not available for history builds.

See also:

Concepts: Build History | Build Queue
Administrator's Guide: Triggering a Custom Build