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

Pre-Tested (Delayed) Commit

Last modified: 06 May 2020

//: # (title: Pre-Tested (Delayed) Commit) //: # (auxiliary-id: Pre-Tested (Delayed) Commit)

An approach which prevents committing defective code into a build, so the entire team's process is not affected. The diagrams on the JetBrains TeamCity web pages provide visualization of the TeamCity approach described below.

The submitted code changes go through testing first. If the code passes all the tests, TeamCity can automatically submit the changes to the version control. From there, the changes will automatically be integrated into the next build. If any test fails, the code is not committed, and the submitting developer is notified.

Developers test their changes by performing a Remote Run. A pre-tested commit is enabled when the commit changes if successful option is selected.

The pre-tested commit is initiated via a plugin to one of supported IDEs. For remote run a command-line tool is also available.

For Git and Mercurial the recommended way to use Branch Remote Run Trigger approach to run personal builds off branches.