Jump to content

Gated commit

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by TeamBuild2020 (talk | contribs) at 10:12, 18 August 2014 (linkfix). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A Gated Commit or also called Gated Check-In [1] is a software build pattern that reduces the chances for breaking a build by committing trivial changes into the main branch of a Revision Control (VCS). In most cases this pattern must be supported by the continuous integration (CI) server. [2]

to perform a gated commit the software developer requests a gated commit from the CI server the before committing the actual changes. The CI server merges the local changes with the head of the master branch and performs a build. So the developer can see if his changes break the build without actually committing the changes.

As an alternative this pattern can be realized using different branches in a VCS.[3]

References

  1. ^ "Use a gated check-in build process to validate changes". Retrieved 2014-08-18.
  2. ^ "Build Pattern: Gated Commit". Retrieved 2014-08-18.
  3. ^ "Gated commits using Git branches". Retrieved 2014-08-18.