TeamCity provides the pre-tested (delayed) commit option to let you commit your changes automatically if the personal build finishes matching predefined conditions. You can commit changes manually, if you did not enable the pre-tested commit option for a build or if your personal build has failed but you still want to commit these particular changes to the version control.
Please note that the pre-tested commit option is not available in Git-based projects.
In Git-based projects, use the Remote run or Remote run for Outgoing Changes feature.
This option is disabled if a change list for the remote run contains Git-files, or a project contains a Git VCS root
and outgoing changes (committed locally, but not yet pushed to the remote repository).
- Start Remote run procedure and customize its general options.
- To enable pre-tested commit, in the Remote Run dialog box, select the Commit after build(s) finish (pre-tested commit) check box,
and then specify the pre-tested commit conditions.
Optionally, in this dialog box, select the Ask for confirmation before commit check box to confirm committing changes if the finished build matches pre-tested commit condition. - Click Submit to run the build.
-
If you have selected the Ask for confirmation before commit check box, to commit your changes,
click the Commit button in the Confirm Commit dialog that will open.
