# 5.1. Buildbot `3.11.9` ( `2024-10-13` )

## 5.1.1. Bug fixes

- Fixed missing builder force scheduler route `/builders/:builderid/force/:scheduler`.

- Fixed URL of WGSI dashboards to keep backward compatibility with the old non-React WSGI plugin.

- Fixed display of long property values by wrapping them

# 5.2. Buildbot `3.11.8` ( `2024-09-27` )

## 5.2.1. Bug fixes

- Made Tags column in Builders page take less space when there are no tags.

- Fixed cropped change author avatar image in web UI.

- Correctly pluralize build count in build summaries in the web UI.

- The change details page no longer requires an additional mouse click to show the change details.

- Fixed showing misleading “Loading” spinner when a change has no builds.

- Fixed too small spacing in change header text in web UI.

- Fixed showing erroneous zero changes count in the web UI when loading changes.

- Cleaned up build and worker tabs in builders view in web UI.

- Improved visual separation between pending build count and build status in trigger build steps in web UI.

## 5.2.2. Changes

- Buildbot has migrated to `quay.io` container registry for storing released container images. In order to migrate to the new registry container image name in `FROM` instruction in Dockerfiles needs to be adjusted to `quay.io/buildbot/buildbot-master` or `quay.io/buildbot/buildbot-worker`.

- The list of supported browsers has been updated to Chrome >=80, Firefox >= 80, Edge >=80, Safari >= 14, Opera >=67.

## 5.2.3. Features

- Add a “Workers” tab to the Builder view listing workers that are assigned to this builder (issue #7162)

- The text displayed in build links is now configurable and can use any build property. It was showing build number or branch and build number before.

- Changes and builds tables in various places in the web UI now have a button to load more items.

# 5.3. Buildbot `3.11.7` ( `2024-08-01` )

## 5.3.1. Bug fixes

- Fixed `GitPoller` when repourl has the port specified (issue #7822)

- Fixed `ChoiceStringParameter` fields with `multiple` would not store the selected values

- Fixed unnecessary trimming of spaces in logs showed in the web UI (issue #7774)

- Fixed favicon colors on build views in the web UI

- Fixed the icon on the about page in the web UI

- Fixed a regression where builds in waterfall view were no longer linking to the build page.

## 5.3.2. Changes

- Buildbot will now error when configured with multiple services of the same type are configured with the same name (issue #6987)

# 5.4. Buildbot `3.11.6` ( `2024-07-12` )

## 5.4.1. Bug fixes

- Transfer build steps (`FileUpload`, `DirectoryUpload`, `MultipleFileUpload`, `FileDownload`, and `StringDownload`) now correctly remove destination on failure, no longer leaving partial content (issue #2860)

- Fixed ReactUI when Buildbot is hosted behind a reverse proxy not at url’s root (issue #7260, issue #7746)

- Fixed results color shown on builder’s header in waterfall view

- Fixed cases where waterfall view could be squashed to a pixel high

- Improved flexibility of scaling_waterfall setting to support floating-point values for more condensed view.

# 5.5. Buildbot `3.11.5` ( `2024-06-24` )

## 5.5.1. Bug fixes

- Fixed several occasional data update glitches in web frontend

- Fixed display of newly added builds in Workers view in the web frontend.

# 5.6. Buildbot `3.11.4` ( `2024-06-20` )

## 5.6.1. Bug fixes

- Fixed a regression where `GitPoller` would no longer register new changes (regression introduced in 3.11.3 in #7554)

# 5.7. Buildbot `3.11.3` ( `2024-05-19` )

## 5.7.1. Bug fixes

- Fixed a bug that caused `GitPoller` running with git configured with `fetch.prune=true` parameter to fail.

- Fixed a bug that caused `GitPoller` to miss changes when buildbot is reconfigured

- Reduced length of directory names produced by `GitPoller` internally. Long directory names could potentially break `GitPoller` on filesystems with low path and name length limits.

- Removed credentials from `repourl` used in the tracker branch name.

## 5.7.2. Deprecations and Removals

- The `pollinterval` (note the small `i`) argument of various change sources has been deprecated with a warning in favor of `pollInterval`.

## 5.7.3. Features

- Added `MessageFormatterFunctionRaw` which allows complete customization of messages to be emitted. This feature has been available since 3.11.0 and only the announcement has been missed.

# 5.8. Buildbot `3.11.2` ( `2024-05-04` )

## 5.8.1. Bug fixes

- Fixed an error in HgPoller when repository initialization fails (issue #7488)

- Updated Makefile to handle Windows paths and Python.

- Added a web configuration setting to select whether build completion or start times are displayed.

- Added revision info column in the web frontend.

- Fixed steps raw log download button.

- Fixed a regression in React UI that prevented hosting Buildbot at a custom URL prefix. This allows to support multiple Buildbot instances on a single server.

## 5.8.2. Improved Documentation

- Documented that `ChangeSource` does not support secrets (or any other renderables), best practice of not encoding secret values in changes and alternative solutions when secret values in changes are unavoidable. `ChangeSource` accidentally supported renderable arguments up until Buildbot 3.7, but this was not documented behavior.

# 5.9. Buildbot `3.11.1` ( `2024-02-24` )

## 5.9.1. Bug fixes

- `GitPoller` now ensures the SSH Private Key it uses has a trailing newline.

- Migrated off python-future which prevented installing Buildbot on distributions that do not provide that package.

- Fix sporadic navigation to builders page when new build is started (issue #7307).

# 5.10. Buildbot `3.11.0` ( `2024-01-25` )

## 5.10.1. Bug fixes

- Declare Python 3.12 compatibility in generated packages of master and worker

## 5.10.2. Features

- Added a new WSGI dashboards plugin for React frontend. It is backwards compatible with AngularJS one but may require changes in CSS styling of displayed web pages.

- Implemented a report generator (`BuildSetCombinedStatusGenerator`) that can access complete information about a buildset.

- Low level database API now has `get_sourcestamps_for_buildset` to get source stamps for a buildset. “/buildsets/:buildsetid/sourcestamps” endpoint has been added to access this from the Data API.

- Added buildset information to dictionaries returned by report generators.

- Added a way to pass additional reporter-specific data to Reporters. Added `extra_info_cb` argument to `MessageFormatter` for this use case.

- Implemented support for report generators in `GerritStatusPush`.

## 5.10.3. Deprecations and Removals

- The `reviewCB`, `reviewArg`, `startCB`, `startArg`, `summaryCB`, `summaryArg`, `builders` , `wantSteps`, `wantLogs` arguments of `GerritStatusPush` have been deprecated.

# 5.11. Buildbot `3.10.1` ( `2023-12-26` )

## 5.11.1. Bug fixes

- Fixed support for Twisted 23.10 and Python 3.12.

- Fixed Data API to have “parent_buildid” key-value pair in messages for rebuilt buildsets (:issue 7222).

- Improved security of tarfile extraction to help avoid CVE-2007-4559. See more details in https://peps.python.org/pep-0706/. Buildbot uses filter=’data’ now. (issue #7294)

- Fixed web frontend package build on certain Python versions (e.g. 3.9).

# 5.12. Buildbot `3.10.0` ( `2023-12-04` )

## 5.12.1. Bug fixes

- `buildbot.changes.bitbucket.BitbucketPullrequestPoller` has been updated to emit the change files.

- Fixed build status key sent to Bitbucket exceeding length limits (issue #7049).

- Fixed a race condition resulting in `EXCEPTION` build results when build steps that are about to end are cancelled.

- Buildrequests are now selected by priority and then by buildrequestid (previously, Buildbot used the age as the secondary sort parameter). This preserves the property of choosing the oldest buildrequest, but makes it predictable which buildrequest will be selected, as there might be multiple buildrequests with the same age.

- Fixed worker to fail a step `uploadDirectory` instead of throwing an exception when directory is not available. (issue #5878)

- Added missing `parent_buildid` and `parent_relationship` keys to the buildset completion event in the Data API.

- Improved handling of Docker containers that fail before worker attaches to master. In such case build will be restarted immediately instead of waiting for a timeout to expire.

- Enhanced the accessibility of secret files by enabling group-readability. Previously, secret files were exclusively accessible to the owner. Now, accessibility has been expanded to allow group members access as well. This enhancement is particularly beneficial when utilizing Systemd’s LoadCredential feature, which configures secrets with group-readable (0o440) permissions.

- `MailNotifier` now works correctly when SSL packages are installed but `useTls=False` and auth (`smtpUser`, `smtpPassword`) is not set. (issue #5609)

- - P4 now reports the correct got_revision when syncing a changelist that only delete files

- - P4 step now use the rev-spec format //{p4client}/…@{revision} when syncing with a revision

- Fixed incorrect propagation of option `--proxy-connection-string` into buildbot.tac when creating new Worker.

- Fixed link to Builder in React Grid View.

- Addressed a number of timing errors in `Nightly` scheduler by upgrading `croniter` code.

## 5.12.2. Changes

- Buildbot will render step properties and check if step should be skipped before acquiring locks. This allows to skip waiting for locks in case step is skipped.

- The `isRaw` and `isCollection` attributes of the `Endpoint` type have been deprecated. `Endpoint` is used to extend the Buildbot API. Us a replacement use the new `kind` attribute.

- `AbstractLatentWorker.check_instance()` now accepts error message being supplied in case instance is not good. The previous API has been deprecated.

- The published Docker image for the worker now uses Debian 11 (Bullseye) as base image.

- The published Docker image for the worker now runs Buildbot in virtualenv.

## 5.12.3. Improved Documentation

- Describe an existing bug with Libvirt latent workers that does not use a copy of the image (:issue 7122).

## 5.12.4. Features

- The new React-based web frontend is no longer experimental. To enable please see the documentation on upgrading to 4.0 for more information. The new web frontend includes the following improvements compared to legacy AngularJS web frontend:

  > - Project support (initially released in Buildbot 3.9.0).

  > - Steps now show the amount of time spent waiting for locks.

  > - The log viewer now supports huge logs without problems.

  > - The log viewer now includes a search box that downloads entire log on-demand without additional button click.

  > - The log viewer now supports downloading log file both as a file and also showing it inline in the browser.

  > - The colors of the website can be adjusted from Buildbot configuration via `www["theme"]` key.

  > - Buildsteps and pending buildrequests have anchor links which allows linking directly to them from external web pages.

- Workers can now be created to use `connection string` right out of the box when new option `--connection-string=` is used.

- Docker Latent workers will now show last logs in Buildbot UI when their startup fails.

- Added `EndpointKind.RAW_INLINE` data API endpoint type which will show the response data inline in the browser instead of downloading as a file.

- Implemented a way to specify volumes for containers spawned by `KubeLatentWorker`.

- `Nightly` scheduler now supports forcing builds at specific times even if `onlyIfChanged` parameter was true and there were no important changes.

- `buildbot.steps.source.p4.P4` can now take a `p4client_type` argument to set the client type (More information on client type [here](https://www.perforce.com/manuals/p4sag/Content/P4SAG/performance.readonly.html))

- Added data and REST APIs to retrieve only projects with active builders.

- Improved step result reporting to specify whether step failed due to a time out.

- Added `tags` option to the `Git` source step to download tags when updating repository.

- Worker now sends `failure_reason` update when the command it was running timed out.

## 5.12.5. Deprecations and Removals

- Legacy AngularJS web frontend will be removed in Buildbot 4.0. Fixes to React web frontend that are regressions from AngularJS web frontend will be backported to 3.x Buildbot series to make migration easier.

- Buildbot Master now requires Python 3.8 or newer. Python 3.7 is no longer supported.

- `buildbot.util.croniter` module has been deprecated in favor of using PyPI `croniter` package.

- `master.data.updates.setWorkerState()` has been deprecated. Use `master.data.updates.set_worker_paused()` and `master.data.updates.set_worker_graceful()` as replacements.

- Buildbot now requires `docker` of version v4.0.0 or newer for Docker support.

- BuildStep instances are now more strict about when their attributes can be changed. Changing attributes of BuildStep instances that are not yet part of any build is most likely an error. This is because such instances are only being used to configure a builder as a source to create real steps from. In this scenario any attribute changes are ignored as far as build configuration is concerned.

  Such changing of attributes has been deprecated and will become an error in the future release.

  For customizing BuildStep after an instance has already been created set_step_arg(name, value) function has been added.

# 5.13. Buildbot `3.9.2` ( `2023-09-02` )

## 5.13.1. Bug fixes

- Work around requirements parsing error for the Twisted dependency by pinning Twisted to 22.10 or older. This fixes buildbot crash on startup when newest Twisted is installed.

# 5.14. Buildbot `3.9.1` ( `2023-09-02` )

## 5.14.1. Bug fixes

- Fixed handling of primary key columns on Postgres in the `copy-db` script.

- Fixed a race condition in the `copy-db` script which sometimes lead to no data being copied.

- Options for create-worker that are converted to numbers are now also checked to be valid Python literals. This will prevent creating invalid worker configurations, e.g.: when using option `--umask=022` instead of `--umask=0o022` or `--umask=18`. (issue #7047)

- Fixed worker not connecting error when there are files in WORKER/info folder that can not be decoded. (issue #3585) (issue #4758) (issue #6932)

- Fixed incorrect git command line parameters when using `Git` source step with `mode="incremental"`, `shallow=True`, `submodules=True` (regression since Buildbot 3.9.0) (issue #7054).

## 5.14.2. Improved Documentation

- Clarified that `shallow` option for the `Git` source step is also supported in `incremental` mode.

# 5.15. Buildbot `3.9.0` ( `2023-08-16` )

## 5.15.1. Bug fixes

- Fixed missed invocations of methods decorated with `util.debounce` when debouncer was being stopped under certain conditions. This caused step and build state string updates to be sometimes missed.

- Improved stale connection handling in `GerritChangeSource`. `GerritChangeSource` will instruct the ssh client to send periodic keepalive messages and will reconnect if the server does not reply for 45 seconds (default). `GerritChangeSource` now has `ssh_server_alive_interval_s` and `ssh_server_alive_count_max` options to control this behavior.

- Fixed unnecessary build started under the following conditions: there is an existing Nightly scheduler, `onlyIfChanged` is set to true and there is version upgrade from v3.4.0 (issue #6793).

- Fixed performance of changes data API queries with custom filters.

- Prevent possible event loss during reconfig of reporters (issue #6982).

- Fixed exception thrown when worker copies directories in Solaris operating system (issue #6870).

- Fixed excessive log messages due to JWT token decoding error (issue #6872).

- Fixed excessive log messages when otherwise unsupported `/auth/login` endpoint is accessed when using `RemoteUserAuth` authentication plugin.

## 5.15.2. Features

- Introduce a way to group builders by project. A new `projects` list is added to the configuration dictionary. Builders can be associated to the entries in that list by the new `project` argument.

  Grouping builders by project allows to significantly clean up the UI in larger Buildbot installations that contain hundreds or thousands of builders for a smaller number of unrelated codebases. This is currently implemented only in experimental React UI.

- Added support specifying the project in `GitHubPullrequestPoller`. Previously it was forced to be equal to GitHub’s repository full name.

- Reporter `BitbucketServerCoreAPIStatusPush` now supports `BuildRequestGenerator` and generates build status for build requests (by default).

- Buildbot now has `copy-db` script migrate all data stored in the database from one database to another. This may be used to change database engine types. For example a sqlite database may be migrated to Postgres or MySQL when the load and data size grows.

- Added cron features like last day of month to `Nightly` Scheduler.

- Buildrequests can now have their priority changed, using the `/buildrequests` API.

- The force scheduler can now set a build request priority.

- Added support for specifying builder descriptions in markdown which is later rendered to HTML for presentation in the web frontend.

- Build requests are now sorted according to their buildrequest. Request time is now used as a secondary sort key.

- Significantly improved performance of reporters or reporters with slower generators which is important on larger Buildbot installations.

- Schedulers can now set a default priority for the buildrequests that it creates. It can either be an integer or a function.

- Implement support for shallow submodule update using git.

- `GerritChangeSource` will now log a small number of previous log lines coming from `ssh` process in case of connection failure.

## 5.15.3. Deprecations and Removals

- Deprecated `projectName` and `projectURL` configuration dictionary keys.

# 5.16. Buildbot `3.8.0` ( `2023-04-16` )

## 5.16.1. Bug fixes

- Fixed compatibility issues with Python 3.11.

- Fixed compatibility with Autobahn v22.4.1 and newer.

- Fixed issue with overriding env when calling ShellMixin.makeRemoteShellCommand

- Buildbot will now include the previous location of moved files when evaluating a Github commit. This fixes an issue where a commit that moves a file out of a folder, would not be shown in the web UI for a builder that is tracking that same folder.

- Improved reliability of Buildbot log watching to follow log files even after rotation. This improves reliability of Buildbot start and restart scripts.

- Fixed handling of occasional errors that happen when attempting to kill a master-side process that has already exited.

- Fixed a race condition in PyLint step that may lead to step throwing exceptions.

- Fixed compatibility with qemu 6.1 and newer when using LibVirtWorker with `cheap_copy=True` (default).

- Fixed an issue with secrets provider stripping newline from ssh keys sent in git steps.

- Fixed occasional errors that happen when killing processes on Windows. TASKKILL command may return code 255 when process has already exited.

- Fixed deleting secrets from worker that contain ‘~’ in their destination path.

## 5.16.2. Changes

- Buildbot now requires NodeJS 14.18 or newer to build the frontend.

- The URLs emitted by the Buildbot APIs have been changed to include slash after the hash (`#`) symbol to be compatible with what React web UI supports.

## 5.16.3. Improved Documentation

- Replace statement “https is unsupported” with a more detailed disclaimer.

## 5.16.4. Features

- Add a way to disable default `WarningCountingShellCommand` parser.

- Added health check API that latent workers can use to specify that a particular worker will not connect and build should not wait for it and mark itself as failure immediately.

- Implemented a way to customize TLS setting for `LdapUserInfo`.

# 5.17. Buildbot `3.7.0` ( `2022-12-04` )

## 5.17.1. Bug fixes

- Improved statistics capture to avoid negative build duration.

- Improved reliability of “buildbot stop” (issue #3535).

- Cancelled builds now have stop reason included into the state string.

- Fixed `custom_class` change hook checks to allow hook without a plugin.

- Added treq response wrapper to fix issue with missing url attribute.

- Fixed Buildbot Worker being unable to start on Python 2.7 due to issue in a new version of Automat dependency.

## 5.17.2. Features

- Expanded `ChangeFilter` filtering capabilities:

    - New `<attribute>_not_eq` parameters to require no match

    - `<attribute>_re` now support multiple regexes

    - New `<attribute>_not_re` parameters to require no match by regex

    - New `property_<match_type>` parameters to perform filtering on change properties.

- Exposed frontend configuration as implementation-defined JSON document that can be queried separately.

- Added support for custom branch keys to `OldBuildCanceller`. This is useful in Version Control Systems such as Gerrit that have multiple branch names for the same logical branch that should be tracked by the canceller.

- `p4port` argument of the `P4` step has been marked renderable.

- Added automatic generation of commands for Telegram bot without need to send them manually to BotFather.

## 5.17.3. Deprecations and Removals

- This release includes an experimental web UI written using React framework. The existing web UI is written using AngularJS framework which is no longer maintained. The new web UI can be tested by installing `buildbot-www-react` package and `'base_react': {}` key-value to www plugins. Currently no web UI plugins are supported. The existing web UI will be deprecated on subsequent Buildbot released and eventually replaced with the React-based web UI on Buildbot 4.0.

# 5.18. Buildbot `3.6.1` ( `2022-09-22` )

## 5.18.1. Bug fixes

- Fixed handling of last line in logs when Buildbot worker 3.5 and older connects to Buildbot master 3.6 (issue #6632).

- Fixed worker `cpdir` command handling when using PB protocol (issue #6539)

# 5.19. Buildbot `3.6.0` ( `2022-08-25` )

## 5.19.1. Bug fixes

- Fixed compatibility with Autobahn 22.4.x.

- Fixed a circular import that causes errors in certain cases.

- Fixed issue with `DockerLatentWorker` accumulating connections with the docker server (issue #6538).

- Fixed documentation build for ReadTheDocs: Sphinx and Python have been updated to latest version.

- Fixed build pending and canceled status reports to GitLab.

- Fixed compatibility of hvac implementation with Vault 1.10.x (issue #6475).

- Fixed a race condition in `PyLint` step that may lead to step throwing exceptions.

- Reporters now always wait for previous report to completing upload before sending another one. This works around a race condition in GitLab build reports ingestion pipeline (issue #6563).

- Fixed “retry fetch” and “clobber on failure” git checkout options.

- Improved Visual Studio installation path retrieval when using MSBuild and only ‘BuildTools’ are installed.

- Fixed search for Visual Studio executables by inspecting both `C:\Program Files` and `C:\Program Files (x86)` directories.

- Fixed Visual Studio based steps causing an exception in `getResultSummary` when being skipped.

- Fixed issue where workers would immediately retry login on authentication failure.

- Fixed sending emails when using Twisted 21.2 or newer (issue #5943)

## 5.19.2. Features

- Implemented support for App password authentication in `BitbucketStatusPush` reporter.

- Cancelled build requests now generate build reports.

- Implemented support for `--no-verify` git option to the `GitCommit` step.

- `HTTPClientService` now accepts full URL in its methods. Previously only a relative URL was supported.

- Callback argument of class `LineBoundaryFinder` is now optional and deprecated.

- Added `VS2019`, `VS2022`, `MsBuild15`, `MsBuild16`, `MsBuild17` steps.

- Names of transfer related temporary files are now prefixed with `buildbot-transfer-`.

- `buildbot try` now accepts empty diffs and prints a warning instead of rejecting the diff.

- Implemented note event handling in GitLab www hook.

## 5.19.3. Deprecations and Removals

- Removed support for Python 3.6 from master. Minimal python version for the master is now 3.7. The Python version requirements for the worker don’t change: 2.7 or 3.4 and newer.

- `buildbot` package now requires Twisted versions >= 18.7.0

# 5.20. Buildbot `3.5.0` ( `2022-03-06` )

## 5.20.1. Bug fixes

- Improved handling of “The container operating system does not match the host operating system” error on Docker on Windows to mark the build as erroneous so that it’s not retried.

- Fixed rare `AlreadyCalledError` exceptions in the logs when worker worker connection is lost at the same time it is delivering final outcome of a command.

- Fixed errors when accessing non-existing build via REST API when an endpoint matching rule with builder filter was present.

- Fixed an error in `CMake` passing options and definitions on the cmake command line.

- Fixed an error when handling command management errors on the worker side (regression since v3.0.0).

- Fixed updating build step summary with mock state changes for MockBuildSRPM and MockRebuild.

- Fixed support for optional `builder` parameter used in RebuildBuildEndpointMatcher (issue #6307).

- Fixed error that caused builds to become stuck in building state until next master restart if builds that were in the process of being interrupted lost connection to the worker.

- Fixed Gerrit change sources to emit changes with proper branch name instead of one containing `refs/heads/` as the prefix.

- Fixed handling of `build_wait_timeout` on latent workers which previously could result in latent worker being shut down while a build is running in certain scenarios (issue #5988).

- Fixed problem on MySQL when using master names or builder tags that differ only by case.

- Fixed timed schedulers not scheduling builds the first time they are enabled with `onlyIfChanged=True` when there are no important changes. In such case the state of the code is not known, so a build must be run to establish the baseline.

- Switched Bitbucket OAuth client from the deprecated ‘teams’ APIs to the new ‘workspaces’ APIs

- Fixed errors when killing a process on a worker fails due to any reason (e.g. permission error or process being already exited) (issue #6140).

- Fixed updates to page title in the web UI. Web UI now shows the configured buildbot title within the page title.

## 5.20.2. Improved Documentation

- Fixed brackets in section 2.4.2.4 - How to populate secrets in a build (issue #6417).

## 5.20.3. Features

- The use of Renderables when constructing payload For JSONStringDownload is now allowed.

- Added `alwaysPull` support when using `dockerfile` parameter of `DockerLatentWorker`.

- Base Debian image has been upgraded to Debian Bullseye for the Buildbot master.

- Added rendering support to `docker_host` and `hostconfig` parameters of `DockerLatentWorker`.

- `MailNotifier` reporter now sends HTML messages by default.

- `MessageFormatter` will now use a default subject value if one is not specified.

- The default templates used in message formatters have been improved to supply more information. Separate default templates for html messages have been provided.

- Added `buildbot_title`, `result_names` and `is_buildset` keys to the data passed to `MessageFormatter` instances for message rendering.

- Added `target` support when using `dockerfile` parameter of `DockerLatentWorker`.

- Simplified `prioritizeBuilders` default function to make an example easier to customize.

- Buildbot now exposes its internal framework for writing tests of custom build steps. Currently the API is experimental and subject to change.

- Implemented detection of too long step and builder property names to produce errors at config time if possible.

## 5.20.4. Deprecations and Removals

- Deprecated `subject` argument of `BuildStatusGenerator` and `BuildSetStatusGenerator` status generators. Use `subject` argument of corresponding message formatters.

# 5.21. Buildbot `3.4.1` ( `2022-02-09` )

## 5.21.1. Bug fixes

- Updated Bitbucket API URL for `BitbucketPullrequestPoller`.

- Fixed a crash in `BitbucketPullrequestPoller` (issue #4153)

- Fixed installation of master and worker as Windows service from wheel package (regression since 3.4.0) (issue #6294)

- Fixed occasional exceptions when using Visual Studio steps (issue #5698).

- Fixed rare “Did you maybe forget to yield the method” errors coming from the log subsystem.

# 5.22. Buildbot `3.4.0` ( `2021-10-15` )

## 5.22.1. Bug fixes

- Database migrations are now handled using Alembic (1.6.0 or newer is required) (issue #5872).

- AMI for latent worker is now set before making spot request to enable dynamically setting AMIs for instantiating workers.

- Fixed `GitPoller` fetch commands timing out on huge repositories

- Fixed a bug that caused Gerrit review comments sometimes not to be reported.

- Fixed a critical bug in the `MsBuild141` step (regression since Buildbot v2.8.0) (issue #6262).

- Implemented renderable support in secrets list of `RemoveWorkerFileSecret`.

- Fixed issues that prevented Buildbot from being used in Setuptools 58 and newer due to dependencies failing to build (issue #6222).

## 5.22.2. Improved Documentation

- Fixed help text for `buildbot create-master` so it states that `--db` option is passed verbatim to `master.cfg.sample` instead of `buildbot.tac`.

- Added documentation of properties available in the formatting context that is presented to message formatters.

## 5.22.3. Features

- MsBuild steps now handle correctly rebuilding or cleaning a specific project. Previously it could only be done on the entire solution.

- Implemented support for controlling `filter` option of `git clone`.

- Optimized build property filtering in the database instead of in Python code.

- Implemented support of `SASL PLAIN` authentication to `IRC` reporter.

- The `want_logs` (previously `wantLogs`) argument to message formatters will now imply `wantSteps` if selected.

- Added information about log URLs to message formatter context.

- Implemented a way to ask for only logs metadata (excluding content) in message formatters via `want_logs` and `want_logs_content` arguments.

- Implemented support for specifying pre-processor defines sent to the compiler in the `MsBuild` steps.

- Introduced `HvacKvSecretProvider` to allow working around flaws in `HashiCorpVaultSecretProvider` (issue #5903).

- Implemented support for proxying worker connection through a HTTP proxy.

## 5.22.4. Deprecations and Removals

- The `wantLogs` argument of message formatters has been deprecated. Please replace any uses with both `want_logs` and `want_logs_content` set to the same value.

- The `wantProperties` and `wantSteps` arguments of message formatters have been renamed to `want_properties` and `want_steps` respectively.

- Buildbot now requires SQLAlchemy 1.3.0 or newer.

# 5.23. Buildbot `3.3.0` ( `2021-07-31` )

## 5.23.1. Bug fixes

- Fixed support of SQLAlchemy v1.4 (issue #5992).

- Improved default build request collapsing functionality to take into account properties set by the scheduler and not collapse build requests if they differ (issue #4686).

- Fixed a race condition that would result in attempts to complete unclaimed buildrequests (issue #3762).

- Fixed a race condition in default buildrequest collapse function which resulted in two concurrently submitted build requests potentially being able to cancel each other (issue #4642).

- The `comment-added` event on Gerrit now produces the same branch as other events such as `patchset-created`.

- `GerritChangeSource` and `GerritEventLogPoller` will now produce change events with `branch` attribute that corresponds to the actual git branch on the repository.

- Fixed handling of `GitPoller` state to not grow without bounds and eventually exceed the database field size. (issue #6100)

- Old browser warning banner is no longer shown for browsers that could not be identified (issue #5237).

- Fixed worker lock handling that caused max lock count to be ignored (issue #6132).

## 5.23.2. Features

- Buildbot can now be configured (via `FailingBuildsetCanceller`) to cancel unfinished builds when a build in a buildset fails.

- `GitHubEventHandler` can now configure authentication token via Secrets management for GitHub instances that do not allow anonymous access

- Buildbot can now be configured (via `OldBuildCanceller`) to cancel unfinished builds when branches on which they are running receive new commits.

- Buildbot secret management can now be used to configure worker passwords.

- Services can now be forced to reload their code via new `canReconfigWithSibling` API.

## 5.23.3. Deprecations and Removals

- `changes.base.PollingChangeSource` has been fully deprecated as internal uses of it were migrated to replacement APIs.

# 5.24. Buildbot `3.2.0` ( `2021-06-17` )

## 5.24.1. Bug fixes

- Fixed occasional `InvalidSpotInstanceRequestID.NotFound` errors when using spot instances on EC2. This could have lead to Buildbot launching zombie instances and not shutting them down.

- Improved `GitPoller` behavior during reconfiguration to exit at earliest possible opportunity and thus reduce the delay that running `GitPoller` incurs for the reconfiguration.

- The docker container for the master now fully builds the www packages. Previously they were downloaded from pypi which resulted in downloading whatever version was newest at the time (issue #4998).

- Implemented time out for master-side utility processes (e.g. `git` or `hg`) which could break the respective version control poller potentially indefinitely upon hanging.

- Fixed a regression in the `reconfig` script which would time out instead of printing error when configuration update was not successfully applied.

- Improved buildbot restart behavior to restore the worker paused state (issue #6074)

- Fixed support for binary patch files in try client (issue #5933)

- Improved handling of unsubscription errors in WAMP which will no longer crash the unsubscribing component and instead just log an error.

- Fixed a crash when a worker is disconnected from a running build that uses worker information for some of its properties (issue #5745).

## 5.24.2. Improved Documentation

- Added documentation about installation Buildbot worker as Windows service.

## 5.24.3. Features

- `DebPbuilder` now supports the `--othermirror` flag for including additional repositories

- Implemented support for setting docker container’s hostname

- The libvirt latent worker will now wait for the VM to come online instead of disabling the worker during connection establishment process. The VM management connections are now pooled by URI.

- Buildbot now sends metadata required to establish connection back to master to libvirt worker VMs.

- `LibVirtWorker` will now setup libvirt metadata with details needed by the worker to connect back to master.

- The docker container for the master has been switched to Debian. Additionally, buildbot is installed into a virtualenv there to reduce chances of conflicts with Python packages installed via `dpkg`.

- BitbucketStatusPush now has renderable build status key, name, and description.

- Pausing a worker is a manual operation which the quarantine timer was overwriting. Worker paused state and quarantine state are now independent. (issue #5611)

- Reduce buildbot_worker wheel package size by 40% by dropping tests from package.

## 5.24.4. Deprecations and Removals

- The connection argument of the LibVirtWorker constructor has been deprecated along with the related Connection class. Use uri as replacement.

- The `*NewStyle` build step aliases have been removed. Please use equivalent steps without the `NewStyle` suffix in the name.

- Try client no longer supports protocol used by Buildbot older than v0.9.

# 5.25. Buildbot `3.1.1` ( `2021-04-28` )

## 5.25.1. Bug fixes

- Fix missing VERSION file in buildbot_worker wheel package (issue #5948, issue #4464).

- Fixed error when attempting to specify `ws_ping_interval` configuration option (issue #5991).

# 5.26. Buildbot `3.1.0` ( `2021-04-05` )

## 5.26.1. Bug fixes

- Fixed usage of invalid characters in temporary file names by git-related steps (issue #5949)

- Fixed parsing of URLs of the form https://api.bitbucket.org/2.0/repositories/OWNER/REPONAME in BitbucketStatusPush. These URLs are in the sourcestamps returned by the Bitbucket Cloud hook.

- Brought back the old (pre v2.9.0) behavior of the `FileDownload` step to act more gracefully by returning `FAILURE` instead of raising an exception when the file doesn’t exist on master. This makes use cases such as `FileDownload(haltOnFailure=False)` possible again.

- Fixed issue with `getNewestCompleteTime` which was returning no completed builds, although it could.

- Fixed the `Git` source step causing last active branch to point to wrong commits. This only affected the branch state in the local repository, the checked out code was correct.

- Improved cleanup of any containers left running by `OpenstackLatentWorker`.

- Improved consistency of log messages produced by the reconfig script. Note that this output is not part of public API of Buildbot and may change at any time.

- Improved error message when try client cannot create a build due to builder being not configured on master side.

- Fixed exception when submitting builds via try jobdir client when the branch was not explicitly specified.

- Fixed handling of secrets in nested folders by the vault provider.

## 5.26.2. Features

- Implemented report generator for new build requests

- Allow usage of Basic authentication to access GitHub API when looking for avatars

- Added support for default Pylint message that was changed in v2.0.

- Implemented support for configurable timeout in the reconfig script via new `progress_timeout` command-line parameter which determines how long it waits between subsequent progress updates in the logs before declaring a timeout.

- Implemented `GitDiffInfo` step that would extract information about what code has been changed in a pull/merge request.

- Add support `--submodule` option for the `repo init` command of the Repo source step.

## 5.26.3. Deprecations and Removals

- `MessageFormatter` will receive the actual builder name instead of `whole buildset` when used from `BuildSetStatusGenerator`.

# 5.27. Buildbot `3.0.3` ( `2021-04-05` )

## 5.27.1. Bug fixes

- Fixed a race condition in log handling of `RpmLint` and `WarningCountingShellCommand` steps resulting in steps crashing occasionally.

- Fixed incorrect state string of a finished buildstep being sent via message queue (issue #5906).

- Reduced flickering of build summary tooltip during mouseover of build numbers (issue #5930).

- Fixed missing data in Owners and Worker columns in changes and workers pages (issue #5888, issue #5887).

- Fixed excessive debug logging in `GerritEventLogPoller`.

- Fixed regression in pending buildrequests UI where owner is not displayed anymore (issue #5940).

- Re-added support for `lazylogfiles` argument of `ShellCommand` that was available in old style steps.

# 5.28. Buildbot `3.0.2` ( `2021-03-16` )

## 5.28.1. Bug fixes

- Updated Buildbot requirements to specify sqlalchemy 1.4 and newer as not supported yet.

# 5.29. Buildbot `3.0.1` ( `2021-03-14` )

## 5.29.1. Bug fixes

- Fixed special character handling in avatar email URLs.

- Fixed errors when an email address matches GitHub commits but the user is unknown to it.

- Added missing report generators to the Buildbot plugin database (issue #5892)

- Fixed non-default mode support for `BuildSetStatusGenerator`.

# 5.30. Buildbot `3.0.0` ( `2021-03-08` )

This release includes all changes up to Buildbot `2.10.2`.

## 5.30.1. Bug fixes

- Avatar caching is now working properly and size argument is now handled correctly.

- Removed display of hidden steps in the build summary tooltip.

- `GitHubPullrequestPoller` now supports secrets in its `token` argument (issue #4921)

- Plugin database will no longer issue warnings on load, but only when a particular entry is accessed.

- SSH connections are now run with `-o BatchMode=yes` to prevent interactive prompts which may tie up a step, reporter or change source until it times out.

## 5.30.2. Features

- `BitbucketPullrequestPoller`, `BitbucketCloudEventHandler`, `BitbucketServerEventHandler` were enhanced to save PR entries matching provided masks as build properties.

- `BitbucketPullrequestPoller` has been enhanced to optionally authorize Bitbucket API.

- Added pullrequesturl property to the following pollers and change hooks: `BitbucketPullrequestPoller`, `GitHubPullrequestPoller`, `GitHubEventHandler`. This unifies all Bitbucket and GitHub pollers with the shared property interface.

- AvatarGitHub class has been enhanced to handle avatar based on email requests and take size argument into account

- Added support for Fossil user objects for use by the buildbot-fossil plugin.

- A new `www.ws_ping_interval` configuration option was added to avoid websocket timeouts when using reverse proxies and CDNs (issue #4078)

## 5.30.3. Deprecations and Removals

- Removed deprecated `encoding` argument to `BitbucketPullrequestPoller`.

- Removed deprecated support for constructing build steps from class and arguments in `BuildFactory.addStep()`.

- Removed support for deprecated `db_poll_interval` configuration setting.

- Removed support for deprecated `logHorizon`, `eventHorizon` and `buildHorizon` configuration settings.

- Removed support for deprecated `nextWorker` function signature that accepts two parameters instead of three.

- Removed deprecated `status` configuration setting.

- `LoggingBuildStep` has been removed.

- `GET`, `PUT`, `POST`, `DELETE`, `HEAD`, `OPTIONS` steps now use new-style step implementation.

- `MasterShellCommand` step now uses new-style step implementation.

- `Configure`, `Compile`, `ShellCommand`, `SetPropertyFromCommand`, `WarningCountingShellCommand`, `Test` steps now use new-style step implementation.

- Removed support for old-style steps.

- Python 3.5 is no longer supported for running Buildbot master.

- The deprecated `HipChatStatusPush` reporter has been removed.

- Removed support for the following deprecated parameters of `HttpStatusPush` reporter: `format_fn`, `builders`, `wantProperties`, `wantSteps`, `wantPreviousBuild`, `wantLogs`, `user`, `password`.

- Removed support for the following deprecated parameters of `BitbucketStatusPush` reporter: `builders`, `wantProperties`, `wantSteps`, `wantPreviousBuild`, `wantLogs`.

- Removed support for the following deprecated parameters of `BitbucketServerStatusPush`, `BitbucketServerCoreAPIStatusPush`, `GerritVerifyStatusPush`, `GitHubStatusPush`, `GitHubCommentPush` and `GitLabStatusPush` reporters: `startDescription`, `endDescription`, `builders`, `wantProperties`, `wantSteps`, `wantPreviousBuild`, `wantLogs`.

- Removed support for the following deprecated parameters of `BitbucketServerPRCommentPush`, `MailNotifier`, `PushjetNotifier` and `PushoverNotifier` reporters: `subject`, `mode`, `builders`, `tags`, `schedulers`, `branches`, `buildSetSummary`, `messageFormatter`, `watchedWorkers`, `messageFormatterMissingWorker`.

- Removed support for the following deprecated parameters of `MessageFormatter` report formatter: `template_name`.

- The deprecated `send()` function that can be overridden by custom reporters has been removed.

- Removed deprecated support for `template_filename`, `template_dir` and `subject_filename` configuration parameters of message formatters.

- The deprecated `buildbot.status` module has been removed.

- The deprecated `MTR` step has been removed. Contributors are welcome to step in, migrate this step to newer APIs and add a proper test suite to restore this step in Buildbot.

- Removed deprecated `buildbot.test.fake.httpclientservice.HttpClientService.getFakeService()` function.

- Removed deprecated support for `block_device_map` argument of EC2LatentWorker being not a list.

- Removed support for deprecated builder categories which have been replaced by tags.