- class buildbot.steps.source.bzr.Bzr
bzr is a descendant of Arch/Baz, and is frequently referred to as simply Bazaar. The repository-vs-workspace model is similar to Darcs, but it uses a strictly linear sequence of revisions (one history per branch) like Arch. Branches are put in subdirectories. This makes it look very much like Mercurial.
from buildbot.plugins import steps
The step takes the following arguments:
baseURLis provided): the URL at which the Bzr source repository is available.
repourlis provided): the base repository URL, to which a branch name will be appended. It should probably end in a slash.
(allowed if and only if
baseURLis provided): this specifies the name of the branch to use when a Build does not provide one of its own. This will be appended to
baseURLto create the string that will be passed to the
bzr checkoutcommand. If
Truethen the branch and revision information that comes with the Build is ignored and branch specified in this parameter is used.
No method is needed for incremental mode. For full mode,
methodcan take the values shown below. If no value is given, it defaults to
This specifies to remove the
workdirand make a full checkout.
This method first runs
bzr clean-treeto remove all the unversioned files then
updatethe repo. This remove all unversioned files including those in .bzrignore.
This is same as fresh except that it doesn’t remove the files mentioned in
.bzrginorei.e, by running
bzr clean-tree --ignore.
A local bzr repository is maintained and the repo is copied to
builddirectory for each build. Before each build the local bzr repo is updated then copied to
buildfor next steps.