The Zuul team is announces the release of Zuul 9.3.0.
Download it from PyPI: https://pypi.org/project/zuul
Find container images at: https://quay.io/organization/zuul-ci
The release notes, included below, are also available in the documentation with hyperlink references:
https://zuul-ci.org/docs/zuul/9.3.0/releasenotes.html
New Features ============
* Monitoring stats for builds are now emitted for more results. Previously they were emitted for some build results such as SUCCESS, FAILURE, and ERROR but now include NODE_FAILURE and other result values.
* Support for using Google Cloud Pub/Sub as an event source has been added to the Gerrit driver.
Upgrade Notes =============
* A significant SQL schema migration is included which requires extra care when upgrading.
It is recommended to make a database backup before upgrading in case of problems. It is also recommended to test the migration with a copy of the database in a development environment first in order to ascertain expected runtime and detect any data integrity problems early.
Zuul is unable to operate as normal during the schema upgrade. The following procedure is recommended:
* Perform a database backup * Stop all Zuul components * Start one scheduler and wait for it to complete the migration and initialization * Start the rest of Zuul
If the migration fails and the backing database is PostgreSQL, the migration will be rolled back and Zuul may be restarted on the previous version. If the backing database is MySQL, if the error happens early enough the migration may be rolled back (look for "Early error in schema migration, rolling back" in scheduler logs). If an error happens late in the migration, manual intervention may be required.
* Zuul's GitHub driver has updated the default merge mode to better align with GitHub's default behavior. This change requires Git 2.33.0 or newer unless you explicitly override Zuul's default merge mode for a project. Additionally, if you aren't overriding the merge mode then the merge algorithm chosen may change depending on your Git and GitHub versions. This is expected to provide more deterministic results.
* Input data from a parent job (return data or artifacts) no longer influences whether a child job can be deduplicated or not.
Bug Fixes =========
* Correct the behavior of the timer driver to not trigger for branches configured as always-dynamic.