Buildbot no longer supports Python 2.7 on the Buildbot master.
This page documents the latest, unreleased version of Buildbot. For documentation for released versions, see http://docs.buildbot.net/current/.
- class buildbot.steps.source.mtn.Monotone¶
from buildbot.plugins import steps factory.addStep(steps.Monotone(repourl='http://path/to/repo', mode='full', method='clobber', branch='some.branch.name', retry=(10, 1)))
Monotone step takes the following arguments:
the URL at which the Monotone source repository is available.
this specifies the name of the branch to use when a Build does not provide one of its own. If
Truethen the branch and revision information that comes with the Build is ignored and branch specified in this parameter is used.
this is a boolean that has a pull from the repository use
--ticker=dotinstead of the default
(optional): defaults to
'incremental'. Specifies whether to clean the build tree or not. In any case, the worker first pulls from the given remote repository to synchronize (or possibly initialize) its local database. The mode and method only affect how the build tree is checked-out or updated from the local database.
The source is update, but any built files are left untouched.
The build tree is clean of any built files. The exact method for doing this is controlled by the
methodargument. Even in this mode, the revisions already pulled remain in the database and a fresh pull is rarely needed.
(optional): defaults to
copywhen mode is
full. Monotone’s incremental mode does not require a method. The full mode has four methods defined:
It removes the build directory entirely then makes fresh checkout from the database.
This remove all other files except those tracked and ignored by Monotone. It will remove all the files that appear in mtn ls unknown. Then it will pull from remote and update the working directory.
This remove all other files except those tracked by Monotone. It will remove all the files that appear in mtn ls ignored and mtn ls unknows. Then pull and update similar to
This first checkout source into source directory then copy the
builddirectory then performs the build operation in the copied directory. This way we make fresh builds with very less bandwidth to download source. The behavior of source checkout follows exactly same as incremental. It performs all the incremental checkout behavior in