Caution

Buildbot no longer supports Python 2.7 on the Buildbot master.

4. Release Notes

4.1. Buildbot 2.2.0 ( 2019-04-07 )

4.1.1. Bug fixes

  • Fix passing the verify and debug parameters for the HttpStatusPush reporter
  • The builder page UI now correctly shows the list of owners for each build.
  • Fixed bug with tilde in git repo url on Python 3.7 (issue # 4639).
  • Fix secret leak when non-interpolated secret was passed to a step (issue # 4007)

4.1.2. Features

  • Added new GitCommit step to perform git commit operation
  • Added new GitTag step to perform git tag operation
  • HgPoller now supports bookmarks in addition to branches.
  • Buildbot can now monitor multiple branches in a Mercurial repository.
  • OAuth2Auth have been adapted to support ref:Secret.
  • Buildbot can now get secrets from the unix password store by zx2c4 (https://www.passwordstore.org/).
  • Added a basename property to the Github pull request webhook handler.
  • The GitHub change hook secret can now be rendered.
  • Each build now gets a preparation step which counts the time spend starting latent worker.
  • Support known_hosts file format as sshKnownHosts parameter in SSH-related operations (issue # 4681)

4.2. Buildbot 2.1.0 ( 2019-03-09 )

4.2.1. Highlights

  • Worker to Master protocol can now be encrypted via TLS.

4.2.2. Bug fixes

  • To avoid database corruption, the upgrade-master command now ignores all signals except SIGKILL. It cannot be interrupted with ctrl-c (issue # 4600).
  • Fixed incorrect tracking of latent worker states that could sometimes result in duplicate stop_instance calls and so on.
  • Fixed a race condition that could manifest in cancelled substantiations if builds were created during insubstantiation of a latent worker.
  • Perforce CLI Rev. 2018.2/1751184 (2019/01/21) is now supported (issue # 4574).
  • Fix encoding issues with Forcescheduler parameters error management code.

4.2.3. Improved Documentation

  • fix grammar mistakes and use Uppercase B for Buildbot

4.2.4. Features

  • Worker now have connection_string kw-argument which can be used to connect to a master over TLS.
  • Adding ‘expand_logs’ option for LogPreview related settings.
  • Force schedulers buttons are now sorted by their name. (issue # 4619)
  • workers now have a new defaultProperties parameter.

4.3. Buildbot 2.0.1 ( 2019-02-06 )

4.3.1. Bug fixes

  • Do not build universal python wheels now that Python 2 is not supported.
  • Print a warning discouraging users from stopping the database migration.

4.4. Buildbot 2.0.0 ( 2019-02-02 )

4.4.1. Deprecations and Removals

  • Removed support for Python <3.5 in the buildbot master code. Buildbot worker remains compatible with python2.7, and interoperability tests are run continuously.
  • APIs that are not documented in the official Buildbot documentation have been made private. Users of these undocumented APIs are encouraged to file bugs to get them exposed.
  • Removed support of old slave APIs from pre-0.9 days. Using old APIs may fail silently. To avoid weird errors when upgrading a Buildbot installation that may use old APIs, first upgrade to to 1.8.0 and make sure there are no deprecated API warnings.
  • Remove deprecated default value handling of the keypair_name and security_name attributes of EC2LatentWorker.
  • Support for Hyper.sh containers cloud provider has been removed as this service has shutdown.

4.4.2. Bug fixes

  • Fix CRLF injection vulnerability with validating user provided redirect parameters (https://github.com/buildbot/buildbot/wiki/CRLF-injection-in-Buildbot-login-and-logout-redirect-code) Thanks to mik317 and mariadb for reporting it.
  • Fix lockup during master shutdown when there’s a build with unanswered ping from the worker and the TCP connection to worker is severed (issue:4575).
  • Fix RemoteUserAuth.maybeAutLogin consumes bytes object as str leading to TypeError during JSON serialization. (issue # 4402)
  • Various database integrity problems were fixed. Most notably, it is now possible to delete old changes without wiping all “child” changes in cascade (issue # 4539, pull request 4536).
  • The GitLab change hook secret is now rendered correctly. (issue # 4118).

4.4.3. Features

  • Identifiers can now contain UTF-8 characters which are not ASCII. This includes worker names, builder names, and step names.

4.5. Buildbot 1.8.0 ( 2019-01-20 )

4.5.1. Bug fixes

  • Fix a regression present in v1.7.0 which caused buildrequests waiting for a lock that got released by an unrelated build not be scheduled (issue # 4491)
  • Don’t run builds that request an instance with incompatible properties on Docker, Marathon and OpenStack latent workers.
  • Gitpoller now fetches only branches that are known to exist on remote. Non-existing branches are quietly ignored.
  • The demo repo in sample configuration files and the tutorial is now fetched via https: instead of git: to make life easier for those behind firewalls and/or using proxies.
  • buildbot sendchange has been fixed on Python 3 (issue # 4138)

4.5.2. Features

  • Add a KubeLatentWorker to launch workers into a kubernetes cluster
  • Simplify/automate configuration of worker as Windows service - eliminate manual configuration of Log on as a service

4.5.3. Deprecations and Removals

  • The deprecated BuildMaster.addBuildset method has been removed. Use BuildMaster.data.updates.addBuildset instead.
  • The deprecated BuildMaster.addChange method has been removed. Use BuildMaster.data.updates.addChange instead.
  • buildbot package now requires Twisted versions >= 17.9.0. This is required for Python 3 support. Earlier versions of Twisted are not supported.

4.6. Buildbot 1.7.0 ( 2018-12-21 )

4.6.1. Bug fixes

  • Fixed JSON decoding error when sending build properties to www change hooks on Python 3.
  • Buildbot no longer attempts to start builds that it can prove will have unsatisfied locks.
  • Don’t run builds that request images or sizes on instances started with different images or sizes.

4.6.2. Features

  • The Buildbot master Docker image at https://hub.docker.com/r/buildbot/ has been upgraded to use Python 3.7 by default.
  • Builder page has been improved with a smoothed build times plot, and a new success rate plot.
  • Allow the Buildbot master initial start timeout to be configurable.
  • An API to check whether an already started instance of a latent worker is compatible with what’s required by a build that is about to be started.
  • Add support for v2 of the Vault key-value secret engine in the SecretInVault secret provider.

4.6.3. Deprecations and Removals

  • Build.canStartWithWorkerForBuilder static method has been made private and renamed to _canAcquireLocks.
  • The Buildbot master Docker image based on Python 2.7 has been removed in favor of a Python 3.7 based image.
  • Builder.canStartWithWorkerForBuilder method has been removed. Use Builder.canStartBuild.

4.7. Buildbot 1.6.0 ( 2018-11-16 )

4.7.1. Bug fixes

  • Fixed missing buildrequest owners in the builder page (issue # 4207, issue # 3904)
  • Fixed display of the buildrequest number badge text in the builder page when on hover.
  • Fix usage of master paths when doing Git operations on worker (issue # 4268)

4.7.2. Improved Documentation

  • Misc improvement in Git source build step documentation.
  • Improve documentation of AbstractLatentWorker.
  • Improve the documentation of the Buildbot concepts by removing unneeded details to other pages.

4.7.3. Features

  • Added a page that lists all pending buildrequests (issue # 4239)
  • Builder page now has a chart displaying the evolution of build times over time
  • Improved FileUpload efficiency (issue # 3709)
  • Add method getResponsibleUsersForBuild in NotifierBase so that users can override recipients, for example to skip authors of changes.
  • Add define parameter to RpmBuild to specify additional –define parameters.
  • Added SSL proxy capability to base web application’s developer test setup (gulp dev proxy --host the-buildbot-host --secure).

4.7.4. Deprecations and Removals

  • The Material design Web UI has been removed as unmaintained. It may be brought back if a maintainer steps up.

4.8. Buildbot 1.5.0 ( 2018-10-09 )

4.8.1. Bug fixes

  • Fix the umask parameter example to make it work with both Python 2.x and 3.x.
  • Fix build-change association for multi-codebase builds in the console view..
  • Fixed builders page doesn’t list workers in multi-master configuration (issue # 4326)
  • Restricted groups added by GitHubAuth’s getTeamsMembership option to only those teams to which the user belongs. Previously, groups were added for all teams for all organizations to which the user belongs.
  • Fix ‘Show old workers’ combo behavior.

4.8.2. Features

  • GitHub teams added to a user’s groups by GitHubAuth’s getTeamsMembership option are now added by slug as well as by name. This means a team named “Bot Builders” in the organization “buildbot” will be added as both buildbot/Bot Builders and buildbot/bot-builders.
  • Make urlText renderable for the FileUpload build step.
  • Added noticeOnChannel option to IRC to send notices instead of messages to channels. This was an option in v0.8.x and removed in v0.9.0, which defaulted to sending notices. The v0.8.x default of sending messages is now restored.

4.8.3. Reverts

  • Reverted: Fix git submodule support when using sshPrivateKey and sshHostKey because it broke other use cases (issue # 4316) In order to have this feature to work, you need to keep your master in 1.4.0, and make sure your worker buildbot.tac are installed in the same path as your master.

4.9. Buildbot 1.4.0 ( 2018-09-02 )

4.9.1. Bug fixes

  • Fix Build.getUrl() to not ignore virtual builders.
  • Fix git submodule support when using sshPrivateKey and sshHostKey settings by passing ssh data as absolute, not relative paths.
  • Fixed P4 for change in latest version of p4 login -p.
  • buildbot.reporters.irc.IrcStatusBot no longer encodes messages before passing them on to methods of its Twisted base class to avoid posting the repr() of a bytes object when running on Python 3.

4.9.2. Features

  • Added new GitPush step to perform git push operations.
  • Objects returned by Renderer now are able to pass extra arguments to the rendered function via withArgs method.

4.9.3. Test Suite

  • Test suite has been improved for readability by adding a lot of inlineCallbacks
  • Fixed tests which didn’t wait for assertFailure’s returned deferred.
  • The test suite now runs on Python 3.7 (mostly deprecation warnings from dependencies shut down)

4.10. Buildbot 1.3.0 ( 2018-07-13 )

4.10.1. Bug fixes

  • buildbot-worker docker image no longer use pidfile. This allows to auto-restart a docker worker upon crash.
  • GitLab v3 API is deprecated and has been removed from http://gitlab.com, so we now use v4. (issue # 4143)

4.10.2. Features

  • -Git now supports sshHostKey parameter to specify ssh public host key for fetch operations.
  • -Git now supports sshPrivateKey parameter to specify private ssh key for fetch operations.
  • -GitPoller now supports sshHostKey parameter to specify ssh public host key for fetch operations. This feature is supported on git 2.3 and newer.
  • -GitPoller now supports sshPrivateKey parameter to specify private ssh key for fetch operations. This feature is supported on git 2.3 and newer.
  • Github hook token validation now uses hmac.compare_digest() for better security

4.10.3. Deprecations and Removals

  • Removed support for GitLab v3 API ( GitLab < 9 ).

4.11. Buildbot 1.2.0 ( 2018-06-10 )

4.11.1. Bug fixes

  • Don’t schedule a build when a GitLab merge request is deleted or edited (issue # 3635)
  • Add GitLab source step; using it, we now handle GitLab merge requests from forks properly (issue # 4107)
  • Fixed a bug in MailNotifier’s createEmail method when called with the default builds value which resulted in mail not being sent.
  • Fixed a Github crash that happened on Pull Requests, triggered by Github Web-hooks. The json sent by the API does not contain a commit message. In github.py this causes a crash, resulting into response 500 sent back to Github and building failure.
  • Speed up generation of api/v2/builders by an order of magnitude. (issue # 3396).

4.11.2. Improved Documentation

  • Added examples/gitlab.cfg to demonstrate integrating Buildbot with GitLab.

4.11.3. Features

  • ForceScheduler Parameters now support an autopopulate parameter.
  • ForceScheduler Parameters ChoiceParameter now correctly supports the strict parameter, by allowing free text entry if strict is False.
  • Allow the remote ref to be specified in the GitHub hook configuration (issue # 3998)
  • Added callable to p4 source that allows client code to resolve the p4 user and workspace into a more complete author. Default behaviour is a lambda that simply returns the original supplied who. This callable happens after the existing regex is performed.

4.12. Buildbot 1.1.2 ( 2018-05-15 )

4.12.1. Bug fixes

  • fix several multimaster issues by reverting issue # 3911. re-opens issue # 3783. (issue # 4067, issue # 4062, issue # 4059)
  • Fix MultipleFileUpload to correctly compute path name when worker and master are on different OS (issue # 4019)
  • LDAP bytes/unicode handling has been fixed to work with Python 3. This means that LDAP authentication, REMOTE_USER authentication, and LDAP avatars now work on Python 3. In addition, an of bounds access when trying to load the value of an empty LDAP attribute has been fixed.
  • Removing `no-select` rules from places where they would prevent the user from selecting interesting text. (issue # 3663)
  • fix `Maximum recursion depth exceeded when lots of worker are trying to connect while master is starting or reconfiguring (issue # 4042).

4.12.2. Improved Documentation

  • Document a minimal secure config for the Buildbot web interface. (issue # 4026)

4.12.3. Features

  • The Dockerfile for the buildbot master image has been updated to use Alpine Linux 3.7. In addition, the Python requests module has been added to this image. This makes GitHub authentication work out of the box with this image. (issue # 4039)
  • New steps for Visual Studio 2017 (VS2017, VC141, and MsBuild141).
  • The smoke tests have been changed to use ES2017 async and await keywords. This requires that the smoke tests run with Node 8 or higher. Use of async and await is recommended by the Protractor team: https://github.com/angular/protractor/blob/master/docs/async-await.md
  • Allow urlText to be set on a url linked to a DirectoryUpload step (issue # 3983)

4.13. Buildbot 1.1.1 ( 2018-04-06 )

4.13.1. Bug fixes

  • Fix issue which marked all workers dis-configured in the database every 24h (issue # 3981 issue # 3956 issue # 3970)
  • The MailNotifier no longer crashes when sending from/to email addresses with “Real Name” parts (e.g., John Doe <john.doe@domain.tld>).
  • Corrected pluralization of text on landing page of the web UI

4.13.2. Improved Documentation

  • Corrected typo in description of libvirt
  • Update sample config to use preferred API

4.13.3. Misc Improvements

  • Home page now contains links to recently active builders

4.14. Buildbot 1.1.0 ( 2018-03-10 )

4.14.1. Deprecations and Removals

  • Removed ramlfication as a dependency to build the docs and run the tests.

4.14.2. Bug fixes

  • Fixed buildrequests API doesn’t provide properties data (issue # 3929)
  • Fix missing owner on builder build table (issue # 3311)
  • Include hipchat as reporter.
  • Fix encoding issues of commands with Windows workers (issue # 3799).
  • Fixed Relax builder name length restriction (issue # 3413).
  • Fix the configuration order so that services can actually use secrets (issue # 3985)
  • Partially fix Builder page should show the worker information (issue # 3546).

4.14.3. Features

  • Added the defaultProperties parameter to builders.
  • When a build step has a log called “summary” (case-insensitive), the Build Summary page will sort that log first in the list of logs, and automatically expand it.

4.15. Buildbot 1.0.0 ( 2018-02-11 )

Despite the major version bump, Buildbot 1.0.0 does not have major difference with the 0.9 series. 1.0.0 is rather the mark of API stability. Developers do not foresee a major API break in the next few years like we had for 0.8 to 0.9.

Starting with 1.0.0, Buildbot will follow semver versioning methodology.

4.15.1. Bug fixes

  • Cloning Git repository with submodules now works with Git < 1.7.6 instead of failing due to the use of the unsupported --force option.
  • GitHub hook now properly creates a change in case of new tag or new branch. GitHub changes will have the category set to tag when a tag was pushed to easily distinguish from a branch push.
  • Fixed issue with Master.expireMasters not always honoring its forceHouseKeeping parameter. (issue # 3783)
  • Fixed issue with steps not correctly ending in CANCELLED status when interrupted.
  • Fix maximum recursion limit issue when transferring large files with LocalWorker (issue:3014).
  • Added an argument to P4Source that allows users to provide a callable to convert Perforce branch and revision to a valid revlink URL. Perforce supplies a p4web server for resolving urls into change lists.
  • Fixed issue with buildbot_pkg` not hanging on yarn step on windows (issue # 3890).
  • Fix issue with workers notify_on_missing not able to be configurable as a single string instead of list of string (issue # 3913).
  • Fixed Builder page should display worker name instead of id (issue # 3901).

4.15.2. Features

  • Add capability to override the default UI settings (issue # 3908)
  • All Reporters have been adapted to be able to use Secret. SVNPoller has been adapted to be able to use Secret.
  • Implement support for Bitbucket Cloud webhook plugin in BitbucketCloudEventHandler
  • The owners property now includes people associated with the changes of the build (issue # 3904).
  • The repo source step now syncs with the --force-sync flag which allows the sync to proceed when a source repo in the manifest has changed.
  • Add support for compressing the repo source step cache tarball with pigz, a parallel gzip compressor.

4.16. Buildbot 0.9.15.post1 ( 2018-01-07 )

4.16.1. Bug fixes

4.17. Buildbot 0.9.15 ( 2018-01-02 )

4.17.1. Bug fixes

  • Fix builder page not showing any build (issue # 3820)
  • Fix double Workers button in the menu. (issue # 3818)
  • Fix bad icons in the worker action dialog.
  • Fix url arguments in Buildbot Badges for python3.
  • Upgrading to guanlecoja-ui version 1.8.0, fixing two issues. Fixed issue where the console view would jump to the top of page when opening the build summary dialog (issue # 3657). Also improved sidebar behaviour by remembering previous pinned vs. collapsed state.
  • Fixes issue with Buildbot DockerLatentWorker, where Buildbot can kill running workers by mistake based on the form the worker name (issue # 3800).
  • Fixes issue with Buildbot DockerLatentWorker not reaping zombies process within its container environment.
  • Update requirement text to use the modern “docker” module from the older “docker-py” module name
  • When multiple reporter or services are configured with the same name, an error is now displayed instead of silently discarding all but the last one issue # 3813.
  • Fixed exception when using buildbot.www.auth.CustomAuth

4.17.2. Features

  • New Buildbot SVG icons for web UI. The web UI now uses a colored favicon according to build results (issue # 3785).
  • paused and graceful Workers States are now stored in the database.
  • Workers States are now displayed in the web UI.
  • Quarantine timers is now using the paused worker state.
  • Quarantine timer is now enabled when a build finish on EXCEPTION state.
  • Standalone binaries for buildbot-worker package are now published for windows and linux (amd64). This allows to run a buildbot-worker without having a python environment.
  • New buildbot-worker create-worker --maxretries for Latent Workers to quit if the master is or becomes unreachable.
  • Badges can now display running as status.
  • The database schema now supports cascade deletes for all objects instead of raising an error when deleting a record which has other records pointing to it via foreign keys.
  • Buildbot can properly find its version if installed from a git archive tarball generated from a tag.
  • Enhanced the test suite to add worker/master protocol interoperability tests between python3 and python2.

4.17.3. Deprecations and Removals

  • buildbot.util.ascii2unicode() is removed. buildbot.util.bytes2unicode() should be used instead.

4.18. Buildbot 0.9.14 ( 2017-12-08 )

4.18.1. Bug fixes

  • Compile step now properly takes the decodeRC parameter in account (issue # 3774)
  • Fix duplicate build requests results in BuildRequestsConnectorComponent when querying the database (issue # 3712).
  • GitPoller now accepts git branch names with UTF-8 characters (issue # 3769).
  • Fixed inconsistent use of pointer style mouse cursor by removing it from the .label css rule and instead creating a new .clickable css rule which is used only in places which are clickable and would not otherwise automatically get the pointer icon, for example it is not needed for hyper-links. (issue # 3795).
  • Rebuilding with the same revision now takes new change properties into account instead of re-using the original build change properties (issue # 3701).
  • Worker authentication is now delayed via a DeferredLock until Buildbot configuration is finished. This fixes UnauthorizedLogin errors during buildbot restart (issue # 3462).
  • Fixes python3 encoding issues with Windows Service (issue # 3796)

4.18.2. Features

  • new :ref`badges` plugin which reimplement the buildbot eight png badge system.
  • In progress worker control API. Worker can now be stopped and paused using the UI. Note that there is no UI yet to look the status of those actions (issue # 3429).
  • Make maximum number of builds fetched on the builders page configurable.
  • Include context in the log message for GitHubStatusPush
  • On ‘Builders’ page reload builds when tags change.
  • Give reporters access to master single in renderables. This allows access to build logs amongst other things
  • Added possibility to check www user credentials with a custom class.

4.19. Buildbot 0.9.13 ( 2017-11-07 )

4.19.1. Deprecations and Removals

Following will help Buildbot to leverage new feature of twisted to implement important features like worker protocol encryption.

  • The buildbot and buildbot-worker packages now requires Python 2.7 or Python 3.4+ – Python 2.6 is no longer supported.
  • buildbot and buildbot-worker packages now required Twisted versions >= 16.1.0. Earlier versions of Twisted are not supported.

4.19.2. Bug fixes

  • Fix Console View forced builds stacking at top (issue:3461)
  • Improve buildrequest distributor to ensure all builders are processed. With previous version, builder list could be re-prioritized, while running the distributor, meaning some builders would never be run in case of master high load. (issue # 3661)
  • Improve getOldestRequestTime function of buildrequest distributor to do sorting and paging in the database layer (issue # 3661).
  • Arguments passed to GitLab push notifications now work with Python 3 (issue # 3720).
  • Web hooks change sources which use twisted.web.http.Request have been fixed to use bytes, not native strings. This ensures web hooks work on Python 3. Please report any issues on web hooks in python3, as it is hard for us to test end to end.
  • Fixed null value of steps and logs in reporter HttpStatusPush api. Fixes (issue # 3180)
  • EC2LatentBuilder now correctly sets tags on spot instances (issue # 3739).
  • Fixed operation of the Try scheduler for a code checked out from Subversion.
  • Fix buildbot worker startup when running as a windows service

4.19.3. Features

  • Make parameters for WarningCountingShellCommand renderable. These are suppressionList, warningPattern, directoryEnterPattern, directoryLeavePattern and maxWarnCount.
  • GitHubEventHandler now supports authentication for GitHub instances that do not allow anonymous access
  • Added support for renderable builder locks. Previously only steps could have renderable locks.
  • Added flag to Docker Latent Worker to always pull images

4.20. Buildbot 0.9.12.post1 ( 2017-10-10 )

This is a release which only exists for the buildbot_grid_view package.

4.20.1. Bug fixes

4.21. Buildbot 0.9.12 ( 2017-10-05 )

4.21.1. Bug fixes

  • Fixed many issues related to connecting masters and workers with different major version of Python (issue # 3416).
  • Fixed KeyError in the log when two buildrequests of the same buildset are finished at the same time (issue # 3472, issue # 3591)
  • Fix for SVN.purge fails when modified files contain non-ascii characters (issue # 3576)
  • Fix the GitHub change hook on Python 3 (issue # 3452).
  • Fix reporters.gitlab to use correct commit status codes (issue # 3641).
  • Fixed deadlock issue, when locks are taken at least 3 times by the 3 Buildstep with same configuration (issue # 3650)
  • Fix the Gerrit source step in the presence of multiple Gerrit repos (issue # 3460).
  • Add empty pidfile option to master and worker start script when –nodaemon option is on. (issue # 3012).

4.21.2. Features

4.21.3. Deprecations and Removals

  • buildbot.util.encodeString() has been removed. buildbot.util.unicode2bytes() should be used instead.

4.22. Buildbot 0.9.11 ( 2017-09-08 )

4.22.1. Incompatible Changes

  • Buildbot is not compatible with python3-ldap anymore. It now requires ldap3 package for its ldap operations (issue # 3530)

4.22.2. Bug fixes

  • Fix issue with logviewer scrolling up indefinitely when loading logs (issue # 3154).
  • Do not add the url if it already exists in the step. (issue # 3554)
  • Fix filtering for REST resource attributes when SQL is involved in the backend (eq, ne, and contains operations, when there are several filters) (issue # 3526).
  • The git source step now uses git checkout -B rather than git branch -M to create local branches (issue # 3537)
  • Fixed Grid View settings. It is now possible to configure “false” values.
  • Fix performance issue when remote command does not send any line boundary (issue # 3517)
  • Fix regression in GithHub oauth2 v3 api, when using enterprise edition.
  • Fix the Perforce build step on Python 3 (issue # 3493)
  • Make REST API’s filter __contains use OR connector rather than AND according to what the documentation suggests.
  • Fixed secret plugins registration, so that they are correctly available in import buildbot.plugins.secrets. changes to all secrets plugin to be imported and used.
  • Fix secrets downloaded to worker with too wide permissions.
  • Fix issue with stop build during latent worker substantiating, the build result was retried instead of cancelled.
  • pip install 'buildbot[bundle]' now installs grid_view plugin. This fixes issues with the tutorial where grid_view is enabled by default.

4.22.3. Improved Documentation

  • Fixed documentation regarding log obfuscation for passwords.
  • Improve documentation of REST API’s __contains filter.

4.22.4. Features

  • Added autopull for Docker images based on config. (issue # 3071)
  • Allow to expose logs to summary callback of GerritStatusPush.
  • Implement GitHub change hook CI skipping (issue # 3443). Now buildbot will ignore the event, if the [ci skip] keyword (configurable) in commit message. For more info, please check out the skip parameter of GitHub hook.
  • GitHubStatusPush now support reporting to ssh style URLs, ie git@github.com:Owner/RepoName.git
  • Added the possibility to filter builds according to results in Grid View.
  • OpenStackLatentWorker now supports V3 authentication.
  • Buildbot now tries harder at finding line boundaries. It now supports several cursor controlling ANSI sequences as well as use of lots of backspace to go back several characters.
  • UI Improvements so that Buildbot build pages looks better on mobile.
  • OpenStackLatentWorker now supports region attribute.
  • The Schedulers builderNames parameter can now be a IRenderable object that will render to a list of builder names.
  • The LdapUserInfo now uses the python3-ldap successor ldap3 (issue # 3530).
  • Added support for static suppressions parameter for shell commands.

4.23. Buildbot 0.9.10 ( 2017-08-03 )

4.23.1. Bug fixes

  • Fix ‘reconfig master causes worker lost’ error (issue # 3392).
  • Fix bug where object names could not be larger than 150 characters (issue # 3449)
  • Fix bug where notifier names could not be overridden (issue # 3450)
  • Fix exception when shutting down a master (issue # 3478)
  • Fix Manhole support to work with Python 3 and Twisted 16.0.0+ (issue # 3160). AuthorizedKeysManhole and PasswordManhole now require a directory containing SSH host keys to be specified.
  • Fix python 3 issue with displaying the properties when fetching builders (issue # 3418).
  • Fix bug when ShellArg arguments were rendered only once during an instance’s lifetime.
  • Fix waterfall tiny size of build status indicators (issue # 3475)
  • Fix waterfall natural order of builder list
  • Fix builder page use ‘pointer’ cursor style for tags (issue # 3473)
  • Fix builder page update tag filter when using the browser’s back button (issue # 3474)

4.23.2. Features

  • added support for builder names in REST API. Note that those endpoints are not (yet) available from the UI, as the events are not sent to the endpoints with builder names.
  • Implemented new ability to set from by email domain. Implemented RolesFromDomain. (issue # 3422)

4.24. Buildbot 0.9.9.post2 ( 2017-07-06 )

4.24.1. Bug fixes

  • Fix tried to complete 100 buildrequests, but only completed 25 issue in buildrequest collapser (issue # 3406)
  • Fixed issue when several mail notifiers are used with same parameters, but different modes (issue # 3398).
  • Fixed release scripts for postN releases

4.25. Buildbot 0.9.9.post1 ( 2017-07-01 )

4.25.1. Bug fixes

  • Fix regression with GitHubAuth when API v3 is used.
  • When using the GitHubAuth v4 API, the generated GraphQL to get the user organizations uses a name alias for each organization. These aliases must not contain dashes.

4.26. Buildbot 0.9.9 ( 2017-06-29 )

4.26.1. Bug fixes

  • Fixed a regression inn UserPasswordAuth where a list would create an error.
  • Fix non ascii payload handling in base web hook (issue # 3321).
  • Fixed default buildrequest collapsing (issue # 3151)
  • _wait_for_request() would fail to format a log statement due to an invalid type being passed to log.msg (resulting in a broken build)
  • Fix Windows compatibility with frontend development tool gulp dev proxy (issue # 3359)

4.26.2. Features

  • New Grid View UI plugin.
  • The Change Hooks system is now integrated in the Plugin Infrastructure in Buildbot system, making it easier to subclass hooks. There is still the need to re- factor hook by hook to allow better customizability.
  • The GitHubAuth now allows fetching the user team membership for all organizations the user belongs to. This requires access to a V4 GitHub API(GraphQL).
  • GitLab merge request hook now create a change with repository to be the source repository and branch the source branch. Additional properties are created to point to destination branch and destination repository. This makes GitLabStatusPush push the correct status to GitLab, so that pipeline report is visible in the merge request page.
  • The GitHubEventHandler now allows the inclusion of white-listed properties for push events.
  • Allow sending a comment to a pull request for Bitbucket Server in BitbucketServerPRCommentPush
  • Implement support for Bitbucket Server webhook plugin in BitbucketServerEventHandler

4.27. Buildbot 0.9.8 ( 2017-06-14 )

4.27.1. Core Bug fixes

  • Fix incompatibility issue of UserPasswordAuth with python 3.
  • Fix issue with oauth sequence not working with Firefox (issue # 3306)
  • Update old addChange method to accept the new chdict names if only the new name is present. Fixes issue # 3191.
  • fix bytes vs string issue on python3 with authorization of rest endpoints.

4.27.2. Core Features

  • doStepIf is now renderable.
  • Source step codebase is now renderable.
  • Step names are now renderable.
  • Added giturlparse utility function to help buildbot components like reporters to parse git url from change sources.
  • Factorized the mail reporter to be able to write new message based reporters, for other backend than SMTP.
  • The class Property now allows being used with Python built in comparators. It will return a Renderable which executes the comparison.

4.27.3. Components Bug fixes

  • GitLab reporter now correctly sets the status to running instead of pending when a build starts.
  • GitLab reporter now correctly works when there are multiple codebase, and when the projects names contain url reserved characters.
  • GitLab reporter now correctly reports the status even if there are several sourcestamps. Better parsing of change repository in GitLab reporter so that it understands ssh urls and https url. GitLab reporter do not use the project field anymore to know the repository to push to.

4.27.4. Components Features

  • GitLab hook now supports the merge_request event to automatically build from a merge request. Note that the results will not properly displayed in merge_request UI due to https://gitlab.com/gitlab-org/gitlab-ce/issues/33293
  • Added a https://pushjet.io/ reporter as buildbot.reporters.pushjet.PushjetNotifier
  • New build step Assert Tests a renderable or constant if it evaluates to true. It will succeed or fail to step according to the result.

4.28. Buildbot 0.9.7 ( 2017-05-09 )

4.28.1. Core Bug fixes

4.28.2. Components Bug fixes

  • Allow renderables in options and definitions of step CMake. Currently only dicts and lists with renderables inside are allowed.
  • OAuth Authentication are now working with RolesFromEmails.
  • DockerLatentWorker: _image_exists does not raise anymore if it encounters an image with <none> tag
  • Fix command line parameters for Robocopy step verbose option

4.28.3. Core Features

  • Builds state_string is now automatically computed according to the BuildStep.getResultSummary, BuildStep.description and updateBuildSummaryPolicy from Common Parameters. This allows the dashboards and reporters to get a descent summary text of the build without fetching the steps.
  • New configurators section, which can be used to create higher level configuration modules for Buildbot.
  • New JanitorConfigurator which can be used to create a builder which save disk space by removing old logs from the database.

4.28.4. Components Features

4.29. Buildbot 0.9.6 ( 2017-04-19 )

4.29.1. Core Bug fixes

  • buildbot.www.authz.endpointmatchers.AnyControlEndpointMatcher now actually doesn’t match GET requests. Before it would act like an AnyEndpointMatcher since the GET had a different case.
  • Passing unicode builderNames to ForceScheduler no longer causes an error.
  • Fix issue with :bb:sched::Nightly change classification raising foreign key exceptions (issue # 3021)
  • Fixes an exception found buildbot_net_usage_data._sendWithUrlib when running through the tutorial using Python 3.
  • usePTY configuration of the ShellCommand now works as expected with recent version of buildbot-worker.

4.29.2. Components Bug fixes

  • pollAtLaunch of the GitHubPullrequestPoller now works as expected. Also the author email won’t be displayed as None
  • GerritChangeSource and GerritStatusPush now use the master’s environment including PATH variable to find the ssh binary.
  • SlaveDirectoryUploadCommand no longer throws exceptions because the file “is used by another process” under Windows

4.29.3. UI Bug fixes

  • Fix waterfall scrolling and zooming in current browsers
  • console_view now properly uses revlink metadata to link to changes.
  • Fixed Console View infinite loading spinner when no change have been recorded yet (issue # 3060).

4.29.4. Core Features

  • new Virtual Builders concept for better integration of frameworks which store the build config along side the source code.

4.29.5. Components Features

  • BitBucket now sets the event property on each change to what the X-Event-Key header contains.
  • GitHubPullrequestPoller now adds additional information about the pull request to properties. The property argument is removed and is populated with the repository full name.
  • GitHub now sets the event property on each change to what the X-GitHub-Event header contains.
  • Changed GitHubAuth now supports GitHub Enterprise when setting new serverURL argument.
  • GitLab now sets the event property on each change to what the X-GitLab-Event header contains.
  • GitHub now process git tag push events
  • GitHub now adds more information about the pull request to the properties. This syncs features with GitHubPullrequestPoller
  • GitLab now process git tag push events
  • GitLab now supports authentication with the secret token

4.29.6. UI Features

4.30. Buildbot 0.9.5 ( 2017-03-18 )

4.30.1. Bug fixes

  • Fix issue with compressing empty log
  • Fix issue with db being closed by wrong thread
  • Fix issue with buildbot_worker not closing file handles when using the transfer steps
  • Fix issue with buildbot requesting too many permissions from GitHub’s OAuth
  • Fix HTTPStep to accept json as keyword argument.
  • Updated OpenStackLatentWorker to use keystoneauth1 so it will support latest python-novaclient packages.
  • Include RpmLint step in steps plugins.

4.30.2. Core Features

  • Experimental support for Python 3.5 and 3.6. Note that complete support depends on fixes to be released in Twisted 17.2.0.
  • New experimental Secret Management framework, which allows to securely declare secrets, reusable in your steps.
  • New Writing Dashboards with Flask or Bottle plugin, which allows to write custom dashboard with traditional server side web frameworks.
  • Added AnyControlEndpointMatcher and EnableSchedulerEndpointMatcher for better configurability of the access control. If you have access control to your Buildbot, it is recommended you add AnyControlEndpointMatcher at the end of your access control configuration.
  • Schedulers can now be toggled on and off from the UI. Useful for temporarily disabling periodic timers.

4.30.3. Components Features

  • FileUpload now supports setting the url title text that is visible in the web UI. FileUpload now supports custom description and descriptionDone text.
  • EC2LatentWorker now provides instance id as the instance property enabling use of the AWS toolkit.
  • Add GitHub pull request Poller to list of available changesources.
  • OAuth2LoginResource now supports the token URL parameter. If a user wants to authenticate through OAuth2 with a pre- generated token (such as the access_token provided by GitHub) it can be passed to /auth/login as the token URL parameter and the user will be authenticated to buildbot with those credentials.
  • New reporter GitHubCommentPush can comment on GitHub PRs
  • GitPoller now supports polling tags in a git repository.
  • MultipleFilUpload now supports the glob parameter. If glob is set to True all workersrcs parameters will be run through glob and the result will be uploaded to masterdest
  • Changed OpenStackLatentWorker to default to v2 of the Nova API. The novaclient package has had a deprecation warning about v1.1 and would use v2 anyway.

4.30.4. Deprecations and Removals

4.31. Buildbot 0.9.4 ( 2017-02-08 )

4.31.1. Database upgrade

A database upgrade is necessary for this release (see upgrade-master).

4.31.2. Bug fixes

  • Like for buildbot start, buildbot upgrade-master will now erase an old pidfile if the process is not live anymore instead of just failing.
  • Change properties ‘value’ changed from String(1024) to Text. Requires upgrade master. (bug #3197)
  • When using REST API, it is now possible to filter and sort in descending order at the same time.
  • Fix issue with HttpStatusPush raising datetime is not JSON serializable error.
  • Fix issue with log viewer not properly rendering color codes.
  • Fixed log viewer selection and copy-paste for Firefox (bug #3662).
  • Fix issue with DelayedCalled already called, and worker missing notification email never received.
  • schedulers and change_source are now properly taking configuration change in account with buildbot reconfig.
  • setuptools is now explicitly marked as required. The dependency was previously implicit.
  • buildbotNetUsageData now uses requests if available and will default to HTTP if a bogus SSL implementation is found. It will also correctly send information about the platform type.

4.31.3. Features

  • Buildbot now uses JWT to store its web UI Sessions. Sessions now persist upon buildbot restart. Sessions are shared between masters. Session expiration time is configurable with c['www']['cookie_expiration_time'] see www.

  • Builders page has been optimized and can now be displayed with 4 http requests whatever is the builder count (previously, there was one http request per builder).

  • Builder and Worker page build list now have the numbuilds= option which allows to show more builds.

  • Masters page now shows more information about a master (workers, builds, activity timer)

  • Workers page improvements:

    • Shows which master the worker is connected to.
    • Shows correctly the list of builders that this master is configured on (not the list of buildermaster which nobody cares about).
    • Shows list of builds per worker similar to the builders page.
    • New worker details page displays the list of builds built by this worker using database optimized query.

4.31.4. Deprecations and Removals

  • Some deprecated broken Contrib Scripts were removed.
  • buildbot.www.hooks.googlecode has been removed, since the Google Code service has been shut down.
  • buildbot.util.json has been deprecated in favor of the standard library json. simplejson will not be used anymore if found in the virtualenv.

4.32. Buildbot 0.9.3 ( 2017-01-11 )

4.32.1. Bug fixes

  • Fix BitbucketStatusPush ep should start with / assertion error.
  • Fix duplicate worker use case, where a worker with the same name would make the other worker also disconnect (bug #3656)
  • GitPoller: buildPushesWithNoCommits now rebuilds for a known branch that was updated to an existing commit.
  • Fix issue with log viewer not staying at bottom of the log when loading log lines.
  • Fixed addBuildURLs in Trigger to use results from triggered builds to include in the URL name exposed by API.
  • Fix Wamp mq support by removing debug, debug_amp and debug_app from the mq config, which is not available in latest version of Python Autobahn. You can now use wamp_debug_level option instead.
  • fix issue with factory.workdir AttributeError are not properly reported.

4.32.2. Features

  • Optimize the memory consumption of the log compression process. Buildbot do not load the whole log into memory anymore. This should improve a lot buildbot memory footprint.
  • Changed the build page so that the preview of the logs are shown in live. It is a preview means the last lines of log. How many lines is configurable per user in the user settings page.
  • Log viewer line numbers are no longer selectable, so that it is easier to copy paste.
  • DockerLatentWorker accepts now renderable Dockerfile
  • Renderer function can now return IRenderable objects.
  • new SetProperties which allows to generate and transform properties separately.
  • Handle new workers in windows_service.py script.
  • Sort the builders in the waterfall view by name instead of ID.

4.33. Buildbot 0.9.2 ( 2016-12-13 )

4.33.1. Bug fixes

  • Fix GitHubAuth to retrieve all organizations instead of only those publicly available.
  • Fixed ref to point to branch instead of commit sha in GitLabStatusPush
  • IRC maybeColorize is able to highlight single words and stop colorization at the end. The previous implementation only stopped colorization but not boldface.
  • fix compatibility issue with mysql5 (do not set default value for TEXT column).
  • Fixed addChange in Change to use the revlink configuration option to generate the revlink.
  • fix threading issue in DockerLatentWorker

4.33.2. Features

  • Implement BitbucketAuth.
  • New GerritEventLogPoller poller to poll Gerrit changes via http API.
  • New GerritVerifyStatusPush can send multiple review status for the same Gerrit change.
  • IRC appends the builder URL to a successful/failed build if available
  • MailNotifier now accepts useSmtps parameter for initiating connection over an SSL/TLS encrypted connection (SMTPS)
  • New support for Mesos and Marathon via MarathonLatentWorker. Marathon is a production-grade container orchestration platform for Mesosphere’s Data- center Operating System (DC/OS) and Apache Mesos.
  • password in DockerLatentWorker and HyperLatentWorker, can be None. In that case, they will be auto-generated from random number.
  • BitbucketServerStatusPush now accepts key, buildName, endDescription, startDescription, and verbose parameters to control the JSON sent to Stash.
  • Buildbot can now be configured to deny read access to REST api resources based on authorization rules.