Buildbot no longer supports Python 2.7 on the Buildbot master.
4. Release Notes¶
4.1.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.1.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.2.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.3.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.3.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.4.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.5.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.5.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.5.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.6.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.7.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.7.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.8.1. Bug fixes¶
- Added new
GitCommitstep to perform git commit operation
- Added new
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/).
- Added a
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.9.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
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.9.3. Improved Documentation¶
- fix grammar mistakes and use Uppercase B for Buildbot
4.10.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.11.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
- Support for
Hyper.shcontainers cloud provider has been removed as this service has shutdown.
4.11.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)
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.