In addition to those, each build uses a timestamp (or omits the timestamp to mean the latest) and branch tag (which defaults to HEAD). How Different VC Systems Specify Sources ¶įor CVS, the static specifications are repository and module. This concept does not map perfectly to every version control system.įor example, for CVS, Buildbot must guess that version updates made to multiple files within a short time represent a single change.Ĭhanges can be provided by a variety of ChangeSource types, although any given project will typically have only a single ChangeSource active.Ģ.5.3.1. This usually happens as one of the first steps in a Build. It contains just enough information needed to acquire specific version of the tree when needed. These change sources fall broadly into two categories: pollers which periodically check the repository for updates and hooks, where the repository is configured to notify Buildbot whenever an update occurs.Ī Change is an abstract way that Buildbot uses to represent changes in any of the Version Control Systems it supports. A change source is the mechanism which is used by Buildbot to get information about new changes in a repository maintained by a Version Control System.
0 kommentar(er)
