The Zuul team is pleased to announce the release of Zuul 4.3.0.
Download it from PyPI: https://pypi.org/project/zuul
The release notes, included below, are also available in the
documentation with hyperlink references:
https://zuul-ci.org/docs/zuul/4.3.0/reference/releasenotes.html
New Features
============
* The MQTT reporter now includes artifact information along with build
results.
* Jobs may now specify an alternate scheme to use when preparing
repositories in the workspace. The default remains the same
golang-style, but an alternate scheme called flat is now
available. See job.workspace-scheme for more details.
* Project secrets keys and SSH keys are now stored in Zookeeper. All
private data will be encrypted at rest, which requires a new mandatory
setting keystore.password in zuul.conf.
* For backup purposes the secrets keys and SSH keys will still exist on
the local filesystem of the scheduler as before.
Upgrade Notes
=============
* The internal git repo caches maintained by the mergers and executors
now use a new naming scheme in order to avoid collisions. When
existing executors and mergers are restarted, they will remove their
git repo caches and re-clone repos using the new scheme. Jobs may be
slow to start until the caches are warmed again.
* As project secrets keys and SSH keys are stored encrypted in Zookeeper
the new keystore.password option in zuul.conf is required. Please add
it to your configuration.
Deprecation Notes
=================
* Zuul now correctly handles the rerequested action on check run trigger
definitions (check_run) literally. This has been requested which
doesn’t match the GitHub api. The value requested is now deprecated
and will be removed in a later release.
Bug Fixes
=========
* Fixed a bug where multiple connections of the same type would not
filter trigger events coming from the wrong connection.