Buildbot no longer supports Python 2.7 on the Buildbot master.
4. Release Notes¶
4.1.1. Bug fixes¶
Fixed spam messages to stdout when renderable operators were being used.
Fixed handling of very long lines in the logs during Buildbot startup (issue # 5706).
Fixed logging of error message to
twistd.login case of old git and
progressoption being enabled.
4.1.2. Deprecations and Removals¶
Removed setup of unused
webstatusfeature of autobahn.
4.2.1. Bug fixes¶
Fixed extraneous warnings due to deprecation of
buildbot.statusmodule even when it’s not used (issue # 5693).
The topbar zoom buttons are now cleared when leaving waterfall view.
The waterfall is now re-rendered upon change to masters.
4.3.1. Bug fixes¶
Fixed the profile menu wrapping because the avatar shows more often and hiding the profile name was not kept in sync.
Reverted too early deprecation of the
Reverted accidental too early migration of
MasterShellCommandand HTTP steps to new style (issue # 5674).
4.4.1. Bug fixes¶
GitLabStatusPush(issue # 5664).
Fixed incorrect deprecation notice for the
4.5.1. Bug fixes¶
Fixed a bug preventing the
timeout=Noneparameter of CopyDirectory step from having effect (issue # 3032).
Fixed a bug in
GitHubStatusPushthat would cause silent failures for builders that specified multiple codebases.
Fixed display refresh of breadcrumb and topbar contextual action buttons (issue # 5549)
Throwing an exception out of a log observer while processing logs will now correctly fail the step in the case of new style steps.
Fixed an issue where
git fetchwould break on tag changes by adding the
-foption. This could previously be handled by manually specifying
clobberOnFailure, but as that is rather heavy handed and off by default, this new default functionality will keep Buildbot in sync with the repository it is fetching from.
GitHubStatusPushlogging an error when triggered by the NightlyScheduler
Fixed GitHub webhook event handler when no token has been set
HashiCorpVaultSecretProviderreading secrets attributes, when they are not named
hg heads -r <branch>to
hg heads <branch>because
-roption shows heads that may not be on the wanted branch.
Fixed inconsistent REST api, buildid vs build_number, issue # 3427
Fixed permission denied in
Fixed AssertionError when calling try client with
--dryrunoption (issue # 5618).
Fixed issue with known hosts not working when using git with a version less than 2.3.0
ForceSchedulernow gets Responsible Users from owner property (issue # 3476)
Added support for
refs/pull/###/headref for fetching the issue ID in the GitHub reporter instead of always expecting
Fixed Github v4 API URL
show_old_buildersto have expected effects in the waterfall view.
Latent workers no longer reuse the started worker when it’s incompatible with the requested build.
Fixed handling of submission of non-decoded
byteslogs in new style steps.
Removed usage of distutils.LooseVersion is favor of packaging.version
OpenstackLatentWorkerto use checkConfig/reconfigService structure.
OpenstackLatentWorkerto use correct method when listing images. Updated
OpenstackLatentWorkerto support renderable
Fixed support of renderables for p4base` and
p4brancharguments of the P4 step.
Buildbot now uses pypugjs library instead of pyjade to render pug templates.
Step summary is now updated after the last point where the step status is changed. Previously exceptions in log finish methods would be ignored.
Transfer steps now return
Fixed bytes-related master crash when calling buildbot try (issue # 4488)
The waterfall modal is now closed upon clicking build summary link
The worker will now report low level cause of errors during the command startup.
4.5.2. Improved Documentation¶
Added documentation of how to log to stdout instead of twistd.log.
Added documentation of how to use pdb in a buildbot application.
Fixed import path for plugins
Added documentation about vault secrets handling.
Added UpCloud latent worker
The init flag is now allowed to be set to false in the host config for
Added ability for the browser to auto-complete force dialog form fields.
AvatarGitHub class has been implemented, which lets us display the user’s GitHub avatar.
New reporter has been implemented
BitbucketServerCoreAPIStatusPush. Reporting build status has been integrated into BitbucketServer Core REST API in Bitbucket Server 7.4. Old BitbucketServer Build REST API is still working, but does not provide the new and improved functionality.
A per-build key-value store and related APIs have been created for transient and potentially large per-build data.
Buildbot worker docker image has been upgraded to
Added the ability to copy build properties to the clipboard.
urlTextparameter to the
DirectoryUploadstep is now renderable.
Added the option to hide sensitive HTTP header values from the log in
It is now possible to set
urlTexton a url linked to a
os_auth_argsto pass in authentication for
UbuCowbuildernow support renderables for the step parameters.
A new report generator API has been implemented to abstract generation of various reports that are then sent via the reporters. The
PushoverNotifiersupport this new API via their new
Added rules for Bitbucket to default revlink helpers.
Added counts of the statuses of the triggered builds to the summary of trigger steps
The worker preparation step now shows the worker name.
4.5.4. Deprecations and Removals¶
buildbot.test.fake.httpclientservice.HttpClientService.getFakeService()has been deprecated. Use
getServicemethod of the same class.
MTRstep has been deprecated due to migration to new style steps and the build result APIs. The lack of proper unit tests made it too time-consuming to migrate this step along with other steps. Contributors are welcome to step in, migrate this step and add a proper test suite so that this situation never happens again.
Many steps have been migrated to new style from old style.
This only affects users who use steps as base classes for their own steps. New style steps provide a completely different set of functions that may be overridden. Direct instantiation of step classes is not affected. Old and new style steps work exactly the same in that case and users don’t need to do anything.
The old-style steps have been deprecated since Buildbot v0.9.0 released in October 2016. The support for old-style steps will be removed entirely Buildbot v3.0.0 which will be released in near future. Users are advised to upgrade their custom steps to new-style steps as soon as possible.
A gradual migration path is provided for steps that are likely to be used as base classes. Users need to inherit from
<StepName>NewStyleclass and convert all overridden APIs to use new-style step APIs. The old-style
<StepName>classes will be provided until Buildbot v3.0.0 release. In Buildbot v3.0.0
<StepName>will refer to new-style steps and will be equivalent to
<StepName>NewStylealiases will be removed in Buildbot v3.2.0.
The list of old-style steps that have new-style equivalents for gradual migration is as follows:
Configure(new-style equivalent is
Compile(new-style equivalent is
HTTPStep(new-style equivalent is
OPTIONS(new-style equivalent is
MasterShellCommand(new-style equivalent is
ShellCommand(new-style equivalent is
SetPropertyFromCommand(new-style equivalent is
WarningCountingShellCommand(new-style equivalent is
Test(new-style equivalent is
The list of old-style steps that have been converted to new style without a gradual migration path is as follows:
Additionally, all source steps have been migrated to new style without a gradual migration path. Ability to be used as base classes was not documented and thus is considered unsupported. Please submit any custom steps to Buildbot for inclusion into the main tree to reduce maintenance burden. Additionally, bugs can be submitted to expose needed APIs publicly for which a migration path will be provided in the future.
The list of old-style source steps that have been converted to new style is as follows:
The undocumented and broken RpmSpec step has been removed.
The usage of certain parameters have been deprecated in
PushoverNotifierreporters. They have been replaced by the
generatorsparameter. The support for the deprecated parameters will be removed in Buildbot v3.0. The list of deprecated parameters is as follows:
NotifierBaseclass has been renamed to
HttpStatusPushBaseclass has been deprecated. Please use
sendmethod of the reporters based on
HttpStatusPushBasehas been deprecated. This affects only users who implemented custom reporters that directly or indirectly derive
HttpStatusPushBase. Please use
sendMessageas the replacement. The following reporters have been affected:
BuildBot now requires SQLAlchemy 1.2.0 or newer.
Deprecation warnings have been added to the
buildbot.statusmodule. It has been deprecated in documentation since v0.9.0.
buildbot.interfaces.WorkerTooOldErroris deprecated in favour of
worker_transitionmodule has been removed.
The buildbot worker Docker image has been updated to Ubuntu 20.04.
4.6.1. Bug fixes¶
Fix 100% CPU on large installations when using the changes API (issue # 5504)
Work around incomplete support for codebases in
GerritChangeSource(issue # 5190). This avoids an internal assertion when the configuration file does not specify any codebases.
Add missing VS2017 entry points.
4.7.1. Bug fixes¶
Fix Docker image building for the master which failed due to mismatching versions of Alpine (issue # 5469).
4.8.1. Bug fixes¶
Fix crash in Buildbot Windows service startup code (issue # 5344)
4.9.1. Bug fixes¶
Fix source distribution missing required buildbot.test.fakedb module for unit tests.
Fix crash in trigger step when renderables are used for scheduler names (issue # 5312)
4.10.1. Bug fixes¶
GitHubEventHandlerto include files in Change that comes from a github PR (issue # 5294)
Updated the Docker container buildbot-master to Alpine 3.11 to fix segmentation faults caused by an old version of musl
Base64 encoding logs and attachments sent via email so emails conform to RFC 5322 2.1.1
Handling the case where the BitbucketStatusPush return code is not 200
When cancelling a buildrequest, the reason field is now correctly transmitted all the way to the cancelled step.
Fix Cache-control header to be compliant with RFC 7234 (issue # 5220)
GerritEventLogPollerclass to be declared as entry_point (can be used in master.cfg file)
Git poller: add –ignore-missing argument to git log call to avoid fatal: bad object errors
Log watcher looks for the “tail” utility in the right location on Haiku OS.
Add limit and filtering support for the changes data API as described in issue # 5207
4.10.2. Improved Documentation¶
Make docs build with the latest sphinx and improve rendering of the example HTML file for custom dashboard
Make docs build with Sphinx 3 and fix some typos and incorrect Python module declarations
Interpolateobjects can now be compared. This will generate a renderable that will be evaluated at runtime. see Renderable Comparison.
Added argument count to lock access to allow a lock to consume a variable amount of units
Added arguments pollRandomDelayMin and pollRandomDelayMax to HgPoller, GitPoller, P4Poller, SvnPoller to spread the polling load
4.10.4. Deprecations and Removals¶
Removed _skipChecks from LockAccess as it’s obsolete
4.11.1. Bug fixes¶
Command buildbot-worker create-worker now supports ipv6 address for buildmaster connection.
Fix crash in latent worker stopService() when the worker is insubstantiating (issue # 4935).
Fix race condition between latent worker’s stopService() and substantiate().
GitHubAuthis now using Authorization headers instead of access_token query parameter, as the latter was deprecated by Github. (issue # 5188)
$are available again as a global variable for UI plugins (issue # 5161).
Latent workers will no longer wait for builds to finish when worker is reconfigured. The builds will still be retried on other workers and the operators will not need to potentially wait multiple hours for builds to finish.
p4poller will no longer override Perforce login ticket handling behavior which fixes random crashes (issue # 5042).
4.11.2. Improved Documentation¶
The procedures of upgrading to Buildbot 1.x and 2.x have been clarified in separate documents.
The layout of the specification of the REST API has been improved.
Updated newsfragments README.txt to no longer refer to renamed class
The documentation now uses the read-the-docs theme which is more readable.
A new www badges style was added:
HttpStatusPushBasenow allows you to skip unicode to bytes encoding while pushing data to server
buildbot-worker create-worker --delete-leftover-dirsoption to automatically remove obsolete builder directories
4.12.1. Bug fixes¶
Fix a potential deadlock when interrupting a step that is waiting for a lock to become available.
Prepare unique hgpoller name when using multiple hgpoller for multiple branches (issue # 5004)
Fix hgpoller crash when force pushing a branch (issue # 4876)
Fix mail recipient formatting to make sure address comments are separately escaped instead of escaping the whole To: or CC: header, which is not RFC compliant.
Master side keep-alive requests are now repeated instead of being single-shot (issue # 3630).
The message queues will now wait until the delivered callbacks are fully completed during shutdown.
Fix encoding errors during P4Poller ticket parsing issue # 5148.
Remove server header from HTTP response served by the web component.
Fix multiple race conditions in Telegram reporter that were visible in tests.
The Telegram reporter will now wait until in-progress polls finish during shutdown.
Improve reliability of timed scheduler.
transfer steps now correctly report errors from workers issue # 5058
Warn if Buildbot title in the configuration is too long and will be ignored.
Worker will now wait for any pending keep-alive requests to finish leaving them in indeterminate state during shutdown.
4.12.2. Improved Documentation¶
Mention that QueueRef.stopConsuming() may return a Deferred.
Add the parameter –use-tls to buildbot-worker create-worker to automatically enable TLS in the connection string
Gerrit reporter now passes a tag for versions that support it. This enables filtering out buildbot’s messages.
GerritChangeSourcecoordinate so as not to generate duplicate changes, resolves issue # 4786
Web front end now allows you to configure the default landing page with c[‘www’][‘default_page’] = ‘name-of-page’.
The new option dumpMailsToLog of MailNotifier allows to dump formatted mails to the log before sending.
bb:cfg:workers will now attempt to read
/etc/os-releaseand stores them into worker info as
os_<field>items. Add new interpolation
workerthat can be used for accessing worker info items.
4.13.1. Bug fixes¶
Updates supported browser list so that Ubuntu Chromium will not always be flagged as out of date.
Fixed IRC notification color of cancelled builds.
Updated url in description of worker service for Windows (no functionality impact).
Updated templates of www-badges to support additional padding configuration (issue # 5079)
Fix issue with custom_templates loading path (issue # 5035)
Fix url display when step do not contain any logs (issue # 5047)
4.14.1. Bug fixes¶
Fix crash when reconfiguring changed workers that have new builders assigned to them (issue # 4757, issue # 5027).
DockerLatentWorker: Allow to bind the same volume twice into a worker’s container, Buildbot now requires ‘docker-py’ (nowadays ‘docker’) version 1.2.3+ from 2015.
IRC bot can have authz configured to create or stop builds (issue # 2957).
4.14.2. Improved Documentation¶
Changed PluginList link from trac wiki directly to the GitHub wiki.
Created a TelegramBot for notification and control through Telegram messaging app.
Added support for environment variable P4CONFIG to class
Allow to define behavior for GitCommit when there is nothing to commit.
Add support for revision links to Mercurial poller
Support recursive matching (‘**’) in MultipleFileUpload when glob=True (requires python3.5+ on the worker)
4.15.1. Bug fixes¶
allow committer of a change to be null for new setups (issue # 4987)
custom_templates are now working again.
Locks will no longer allow being acquired more times than the maxCount parameter if this parameter is changed during master reconfiguration.
Improve log cleaning performance by using delete with join on supported databases.
Hiding/showing of inactive builders is now possible in Waterfall view.
Database upgrade may take a while on larger instances on this release due to newly added index.
4.16.2. Bug fixes¶
Add an index to
steps.started_atto boost expensive SQL queries.
Fix handling of the
refs_changedevent in the BitBucket Server web hook.
Fix errors when disconnecting a libvirt worker (issue # 4844).
Fix Bitbucket Cloud hook crash due to changes in their API (issue # 4873).
GerritEventLogPollerwas using the wrong date format.
Fix janitor Exception when there is no logchunk to delete.
Reduced the number of SQL queries triggered by
getPrevSuccessfulBuild()by up to 100.
GitStepMixin: Prevent builders from corrupting temporary ssh data path by using builder name as part of the path
tagNameto be a renderable.
Fix Github error reporting to handle exceptions that happen before the HTTP request is sent.
GitPoller: Trigger on pushes with no commits when the new revision is not the tip of another branch.
Git: Fix the invocation of
git submodule foreachon cleaning.
Fix StatsService not correctly clearing old consumers on reconfig.
Fix various errors in try client with Python 3 (issue # 4765).
Prevent accidental start of multiple force builds in web UI (issue # 4823).
The support for proxying Buildbot frontend to another Buildbot instance during development has been fixed. This feature has been broken since v2.3.0, and is now completely re-implemented for best performance, ease of use and maintainability.
4.16.3. Improved Documentation¶
Document why some listed icons may not work out-of-the-box when building a custom dashboard (issue # 4939).
Improve Vault secrets management documentation and examples.
Link the documentation of
www.portto the capabilities of
Move the documentation on how to submit PRs out of the trac wiki to the documentation shipped with Buildbot, update and enhance it.
Update buildbot worker image to Ubuntu 18.04 (issue # 4928).
DockerLatentWorker: Added support for docker build contexts,
buildargs, and specifying controlling context.
GerritEventLogPollernow populate the
filesattribute of emitted changes when the
get_filesargument is true. Enabling this feature triggers an additional HTTP request or SSH command to the Gerrit server for every emitted change.
Buildbot now warns users who connect using unsupported browsers.
Boost janitor speed by using more efficient SQL queries.
Scheduler properties are now renderable.
strict_warningsoption to fail on warnings.
UI now shows a paginated view for trigger step sub builds.
4.16.5. Deprecations and Removals¶
Support for older browsers that were not working since 2.3.0 has been removed due to technical limitations. Notably, Internet Explorer 11 is no longer supported. Currently supported browsers are Chrome 56, Firefox 52, Edge 13 and Safari 10, newer versions of these browsers and their compatible derivatives. This set of browsers covers 98% of users of buildbot.net.
4.17.1. Bug fixes¶
Fix vulnerability in OAuth where user-submitted authorization token was used for authentication (https://github.com/buildbot/buildbot/wiki/OAuth-vulnerability-in-using-submitted-authorization-token-for-authentication) Thanks to Phillip Kuhrt for reporting it.
Support for older browsers has been hopefully temporarily broken due to frontend changes in progress. Notably, Internet Explorer 11 is not supported in this release. Currently supported browsers are Chrome 56, Firefox 52, Edge 13 and Safari 10, newer versions of these browsers and their compatible derivatives. This set of browsers covers 98% of users of buildbot.net.
4.18.2. Bug fixes¶
Gitto clean the repository after the checkout when submodules are enabled. Previously this action could lead to untracked module directories after changing branches.
Latent workers with negative build_wait_timeout will be shutdown on master shutdown.
Latent worker will now wait until start_instance() before starting stop_instance() or vice-versa. Master will wait for these functions to finish during shutdown.
Latent worker will now correctly handle synchronous exception from the backend worker driver.
Fixed a potential error during database migration when upgrading to versions >=2.0 (issue # 4711).
4.18.3. Deprecations and Removals¶
The support for building Buildbot using npm as package manager has been removed. Please use yarn as a replacement that is used by Buildbot developers.
4.19.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)
GitCommitstep to perform git commit operation
GitTagstep to perform git tag operation
HgPoller now supports bookmarks in addition to branches.
Buildbot can now monitor multiple branches in a Mercurial repository.
OAuth2Authhave been adapted to support ref:Secret.
Buildbot can now get secrets from the unix password store by zx2c4 (https://www.passwordstore.org/).
basenameproperty 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
sshKnownHostsparameter in SSH-related operations (issue # 4681)
Worker to Master protocol can now be encrypted via TLS.
4.20.2. Bug fixes¶
To avoid database corruption, the
upgrade-mastercommand 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_instancecalls 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.20.3. Improved Documentation¶
fix grammar mistakes and use Uppercase B for Buildbot
Workernow 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)
workersnow have a new
4.21.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.22.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
Hyper.shcontainers cloud provider has been removed as this service has shutdown.
4.22.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
mariadbfor 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).
Identifiers can now contain UTF-8 characters which are not ASCII. This includes worker names, builder names, and step names.
5. Older Release Notes¶
- 5.1. Release Notes for Buildbot
- 5.2. Release Notes for Buildbot
- 5.3. Release Notes for Buildbot
- 5.4. Release Notes for Buildbot
- 5.5. Release Notes for Buildbot
- 5.6. Release Notes for Buildbot
- 5.7. Release Notes for Buildbot
- 5.8. Release Notes for Buildbot
- 5.9. Release Notes for Buildbot
- 5.10. Release Notes for Buildbot
- 5.11. Release Notes for Buildbot
- 5.12. Release Notes for Buildbot
- 5.13. Release Notes for Buildbot
- 5.14. Release Notes for Buildbot
- 5.15. Release Notes for Buildbot
- 5.16. Release Notes for Buildbot
- 5.17. Release Notes for Buildbot
- 5.18. Release Notes for Buildbot
- 5.19. Release Notes for Buildbot
- 5.20. Release Notes for Buildbot
- 5.21. Release Notes for Buildbot
- 5.22. Release Notes for Buildbot
- 5.23. Release Notes for Buildbot
- 5.24. Release Notes for Buildbot
- 5.25. Release Notes for Buildbot
- 5.26. Release Notes for Buildbot
- 5.27. Release Notes for Buildbot
- 5.28. Release Notes for Buildbot
- 5.29. Release Notes for Buildbot
- 5.30. Release Notes for Buildbot
- 5.31. Release Notes for Buildbot
- 5.32. Release Notes for Buildbot
- 5.33. Release Notes for Buildbot
- 5.34. Release Notes for Buildbot
- 5.35. Release Notes for Buildbot
- 5.36. Release Notes for Buildbot
- 5.37. Release Notes for Buildbot
- 5.38. Release Notes for Buildbot 0.9.0b9
- 5.39. Release Notes for Buildbot 0.9.0b8
- 5.40. Release Notes for Buildbot 0.9.0b7
- 5.41. Release Notes for Buildbot 0.9.0b6
- 5.42. Release Notes for Buildbot 0.9.0b5
- 5.43. Release Notes for Buildbot 0.9.0b4
- 5.44. Release Notes for Buildbot 0.9.0b3
- 5.45. Release Notes for Buildbot 0.9.0b2
- 5.46. Release Notes for Buildbot 0.9.0b1
- 5.47. Release Notes for Buildbot 0.8.11
- 5.48. Release Notes for Buildbot 0.8.10
- 5.49. Release Notes for Buildbot 0.8.9
- 5.50. Release Notes for Buildbot v0.8.8
- 5.51. Release Notes for Buildbot v0.8.7
- 5.52. Release Notes for Buildbot v0.8.6p1
Note that Buildbot-0.8.11 was never released.