- Zuul-announce - lists.opendev.org

Zuul 3.14.0 released
by corvus＠inaugust.com 20 Dec '19

20 Dec '19

The Zuul team is pleased to announce the release of Zuul 3.14.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/3.14.0/releasenotes.html New Features ============ * Zuul now supports triggering a smart reconfiguration by using the command zuul-scheduler smart-reconfigure. Upgrade Notes ============= * Zuul no longer supports Ansible 2.5 for running jobs.

1 0

Zuul 3.13.0 released
by corvus＠inaugust.com 12 Dec '19

12 Dec '19

The Zuul team is pleased to announce the release of Zuul 3.13.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/3.13.0/releasenotes.html New Features ============ * Zuul now supports Ansible 2.9 for running jobs. Upgrade Notes ============= * The default version of Ansible used by Zuul jobs has been changed to 2.8. See job.ansible-version for more information. * As a result of switching to Ansible 2.8, it is possible for the ansible_python_interpreter version of your nodeset to change to 'auto'. This could result in your jobs now running under a different version of python than prior to this release. See Ansible and Python 3 for additional info. * Ansible 2.6 for Zuul jobs has been marked deprecated and will be removed in a future release.

1 0

Upcoming Zuul release dropping support for Ansible 2.5
by corvus＠inaugust.com 11 Dec '19

11 Dec '19

Ansible 2.5 has been unsupported by the Ansible community for quite some time and therefore an upcoming release of Zuul will drop support for it as well. This process is new to us, and we have not yet formalized our support policy for older Ansible versions. We plan on doing so this week so that in the future, everyone will know when to expect changes like this. Later this week we plan to make two more releases of Zuul to aid folks in this transition: * 3.13.0 will add support for Ansible 2.9 and change the default version of Ansible from 2.7 to 2.8 * 3.14.0 will remove support for Ansible 2.5 If you wish to avoid the default value change to Ansible 2.8, be sure to override that in your configuration[1] before upgrading to 3.13. If you know you have jobs which rely on Ansible 2.5, you will want to pause your upgrades at 3.13 until you can update jobs to work with a later version. Note that since we are removing 2.5 after adding 2.9, you have the widest possible range of versions available during this window. [1] https://zuul-ci.org/docs/zuul/user/config.html#attr-job.ansible-version

1 0

Nodepool 3.10.0 released
by corvus＠inaugust.com 10 Dec '19

10 Dec '19

The Zuul team is pleased to announce the release of Nodepool 3.10.0. Download it from PyPI: https://pypi.org/project/nodepool The release notes, included below, are also available in the documentation with hyperlink references: https://zuul-ci.org/docs/nodepool/3.10.0/releasenotes.html#relnotes-3-10-0 New Features ============ * Nodepool now supports providers.[openstack].post-upload-hook to run a user supplied script after an image has been uploaded to a cloud but before it gets used. Bug Fixes ========= * Fixed compatibility issue with openstacksdk 0.37.0 and above.

1 0

Zuul 3.12.0 released
by corvus＠inaugust.com 10 Dec '19

10 Dec '19

The Zuul team is pleased to announce the release of Zuul 3.12.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/3.12.0/releasenotes.html#relnotes-3-12-0 New Features ============ * A new config option enable executor to not performed global merge job. Upgrade Notes ============= * The Gerrit driver now has an additional option, pipeline.reporter.<gerrit reporter>.comment which may be used to suppress reporting job results as review comments. Due to the configuration syntax for Gerrit reporters, the word “comment” may no longer be used as a review label. Other Notes =========== * The –id option to both the autohold-delete and autohold-info zuul CLI commands has been removed.

1 0

Change to configure-mirrors role to accomodate Python Setuptools update
by Clark Boylan 26 Nov '19

26 Nov '19

Hello, The recent release of setuptools 42.0.0 has broken the method used by the configure-mirrors role to ensure easy_install (the older method to install Python packages, before pip became in widespread use [1]) would only access the PyPI mirror. The prior mirror setup code would set the "allow_hosts" whitelist to the mirror host exclusively in pydistutils.cfg. This would avoid easy_install "leaking" access outside the specified mirror. Change [2] in setuptools means that pip is now used to fetch packages. Since it does not implement the constraints of the "allow_hosts" setting, specifying this option has become an error condition. This is reported as: the `allow-hosts` option is not supported when using pip to install requirements It has been pointed out [3] that this prior code would break any dependency_links [4] that might be specified for the package (as the external URLs will not match the whitelist). Overall, there is no desire to work-around this behaviour as easy_install is considered deprecated for any current use. In short, this means the only solution is to remove the now conflicting configuration from pydistutils.cfg. Due to the urgency of this update, it has been merged with [5] before our usual 2-week deprecation notice. The result of this is that older setuptools (perhaps in a virtualenv) with jobs still using easy_install may not correctly access the specified mirror. Assuming jobs have access to PyPI, they would still work, although without the benefits of a local mirror. If such jobs are firewalled from upstream they may now fail. We consider the chance of jobs using this legacy install method in this situation to be very low. Please contact zuul-discuss [6] with any concerns. We now return you to your regularly scheduled programming :) [1] https://packaging.python.org/discussions/pip-vs-easy-install/ [2] https://github.com/pypa/setuptools/commit/d6948c636f5e657ac56911b71b7a459d3… [3] https://github.com/pypa/setuptools/issues/1916 [4] https://python-packaging.readthedocs.io/en/latest/dependencies.html [5] https://review.opendev.org/695821 [6] http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss

1 0

Nodepool 3.9.0 released
by corvus＠inaugust.com 19 Oct '19

19 Oct '19

The Zuul team is pleased to announce the release of Nodepool 3.9.0. Download it from PyPI: https://pypi.org/project/nodepool The release notes, included below, are also available in the documentation with hyperlink references: https://zuul-ci.org/docs/nodepool/releasenotes.html#relnotes-3-9-0 Upgrade Notes ============= * This release should only be run against Zuul 3.11.1 or greater. Earlier Zuul releases will not convert the new default python-path of auto to /usr/bin/python2 for Ansible <2.8, leading to a configuration error. It may be possible to use earlier Zuul releases if you you are only using Ansible >= 2.8, or explicitly set python-path for every image. New Features ============ * A diskimage can specify the full path to the diskimage-builder command with the dib-cmd configuration parameter. The --fake parameter of nodepool-builder (only used by CI) has been removed and replaced with explicit calls in testing fixtures. * The default python-path is now auto (instead of /usr/bin/python2). With this, Zuul 3.11.1 and greater will set the ansible_python_interpreter to auto when using Ansible >=2.8 to use automated interpreter discovery. When using earlier Ansible, it will remain the old default of /usr/bin/python2. This will remove the need to override python-path explicitly for Python 3-only distributions, which should be detected correctly automatically.

1 0

Zuul 3.11.1 released
by corvus＠inaugust.com 17 Oct '19

17 Oct '19

The Zuul team is pleased to announce the release of Zuul 3.11.1 (a bugfix release immediately following 3.11.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/3.11.1/releasenotes.html#relnotes-3-11-1 3.11.0: Upgrade Notes ============= * The Gerrit driver will now perform query actions over HTTP if an HTTP password is configured. In this situation, the SSH connection is now only used for receiving events. The HTTP password is not required, but it is recommended since it provides more reporting options (including line comments). New Features ============ * Added the pipeline.enqueue reporter action so that reporters may be run when an item is enqueued into a pipeline. * Added the pipeline.no-jobs reporter action so that reporters may be run when an item is dequeued into a pipeline without having run any jobs. * A new zuul CLI command, autohold-info, has been added to retrieve full details for an existing autohold request. * Autohold requests are now stored in ZooKeeper, rather than in memory. As a result of this change, a new zuul CLI command, autohold-delete has been added to remove existing requests. * New scheduler options, max_hold_expiration and default_hold_expiration, are added to control how long nodes held for an autohold request remain available. The max_hold_expiration option defaults to 0, which means the held nodes will not automatically expire, and default_hold_expiration defaults to the value of max_hold_expiration. 3.11.1: Bug Fixes ========= * Fixed a regression where changes with a failing job with soft dependencies would remain in the queue indefinitely.

1 0

Zuul 3.10.2 released (security update)
by corvus＠inaugust.com 18 Sep '19

18 Sep '19

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.

1 0

Behavior change in upload-logs role
by Paul Belanger 06 Sep '19

06 Sep '19

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

1 0