If you write an email parsing function, they can also all be driven by a suitable mail-parsing source.Īdditionally, handlers for web-based notification (i.e. PBChangeSource (listening for connections from a, which is available with Monotone)Īll VC systems can be driven by a PBChangeSource and the buildbot sendchange tool run from some form of commit script.GerritEventLogPoller connects to Gerrit via HTTP with the help of the plugin events-log.GerritChangeSource connects to Gerrit via SSH to get a live stream of changes.GitHubPullrequestPoller (polling GitHub API for pull requests).GitPoller (polling a remote Git repository).GitHub change hook (specifically designed for GitHub notifications, but requiring a publicly-accessible WebStatus).
PBChangeSource (listening for connections from master/contrib/github_buildbot.py, which listens for notifications from GitHub).PBChangeSource (listening for connections from master/contrib/git_buildbot.py run in the post-receive hook).PBChangeSource (listening for connections from master/contrib/bzr_buildbot.py run in a post-change-branch-tip or commit hook).Mail-parsing ChangeSources, though there are no ready-to-use recipes.BitbucketPullrequestPoller (polling Bitbucket for pull requests).HgPoller (polling a remote Mercurial repository).BitBucket change hook (specifically designed for BitBucket notifications, but requiring a publicly-accessible WebStatus).Change Hooks in WebStatus (including master/contrib/hgbuildbot.py, configurable in a changegroup hook).PBChangeSource (listening for connections from master/contrib/darcs_buildbot.py in a commit script).SVNCommitEmailMaildirSource (watching for email sent by ).PBChangeSource (listening for connections from a long-running master/contrib/svn_watcher.py or master/contrib/svnpoller.py polling process.PBChangeSource (listening for connections from master/contrib/svn_buildbot.py run in a postcommit script).PBChangeSource (listening for connections from a long-running master/contrib/viewcvspoll.py polling process which examines the ViewCVS database directly).PBChangeSource (listening for connections from buildbot sendchange run in a loginfo script).CVSMaildirSource (watching mail sent by master/contrib/buildbot_cvs_mail.py script).
Note that some of these modules are in Buildbot’s master/contrib directory, meaning that they have been offered by other users in hopes they may be useful, and might require some additional work to make them functional. There are a variety of ChangeSource classes available, some of which are meant to be used in conjunction with other tools to deliver Change events from the VC repository to the buildmaster.Īs a quick guide, here is a list of VC systems and the ChangeSources that might be useful with them.
TORTOISEHG CREATE SVN REPO HOW TO
This section provides a description of all available ChangeSource types and explains how to set up each of them. This chapter describes how the Buildbot learns about what Changes have occurred.įor more information on VC systems and Changes, see Version Control Systems.Ĭhanges can be provided by a variety of ChangeSource types, although any given project will typically have only a single ChangeSource active. The first step of each Build is typically to acquire a copy of some version of this tree. A Version Control System maintains a source tree, and tells the buildmaster when it changes.
0 kommentar(er)
