The Zuul team is pleased to announce the release of Zuul 3.10.2.
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/3.10.2/releasenotes.html#relnotes-3-10-2
Security Issues
===============
* The synchronize rsh rsync_opts is now prohibited for security reasons
as it could be used to circumvent executor host command execution
restrictions.
New Features
============
* The maximum starting builds depending on cpu cores can be limited
using executor.max_starting_builds configuration.
Bug Fixes
=========
* Under specific conditions Zuul could fail to properly update git repos
causing it to fall back to testing master. If jobs were meant to run
against commits other than current master this lead to testing the
wrong commit. Zuul now correctly updates repos and should test the
correct commit in all cases.
Specifically this could happen if a new branch was created off a
commit in an existing branch. Then the first proposed change to this
new branch would be tested against master instead.
Greetings,
We'd like to make a change[1] to the upload-logs role in an effort to make
it easier for users to view logs by default:
Allow upload-logs to toggle compression of console logs
We should make it easy for users to view console logs by default.
Today, we compress and upload logs and by default apache / nginx will
not properly display them as plain text. This commit changes the
default to not compress, but allows more advanced users to enable this
logic. As mostly likley it also means additional configuration for
your web server.
We've created a new role variable (zuul_log_compress) which will be
false by default. If you wish to keep your logs compressed, you should
toggle this to true. Please refer to existing ML[2] post for more
discussion.
[1] https://review.opendev.org/567696/
[2] http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-May/000412.html