The Zuul team is pleased to announce the release of Zuul 9.1.0.
Download it from PyPI: https://pypi.org/project/nodepool
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/nodepool/9.1.0/releasenotes.html
New Features
============
* The AWS driver now supports an providers.[aws].image-import-timeout
option to control automatic retries and timeouts when AWS import task
resource limits are reached.
* The AWS driver now supports volume quota. It will automatically
register the limits from the cloud and ensure that labels that specify
EBS volume attributes stay under the limit.
* The Azure driver now supports specifying the size of the OS disk.
* The Kubernetes and OpenShift drivers now support adding dynamic
metadata, i.e. Pod and Namespace labels, with information about the
corresponding node request. This is analogous to the existing dynamic
tags of the OpenStack, AWS, and Azure drivers.
See providers.[kubernetes].pools.labels.dynamic-labels,
providers.[openshift].pools.labels.dynamic-labels, and
providers.[openshiftpods].pools.labels.dynamic-labels for details.
* The Azure driver now support specifying community and shared gallery
images.
* The metastatic driver will now automatically use the node-attributes
from backing nodes as default values for node-attributes of metastatic
nodes. Any node-attribute values specified in the metastatic pool
config will override those from the backing node.
* An upload timeout can be configured on OpenStack providers for use in
the case that image uploads to a provider take longer than the default
of one hour.
Upgrade Notes
=============
* The Azure driver now uses the "Standard" SKU for all public IP
addresses. Previously it would chose either "Standard" or "Basic"
depending on the selection of IPv4 or IPv6 addresses.
Pricing for public IP addresses may differ between the SKU levels.
Standard IP addresses block all incoming traffic by default, therefore
the use of a Network Security Group is required in order to allow
incoming traffic.
If you are not currently using a Network Security Group, then before
upgrading Nodepool it is recommended to create one, add any required
rules, and attach it to the subnet that Nodepool uses.
* The Azure driver no longer creates and deletes Disks, Network
Interfaces, or Public IP Addresses as separate steps.
Nodepool and user-supplied tags will no longer be applied to Network
Interfaces, or Public IP Addresses. This also limits Nodepool's
ability to detect leaks of these resources (however this is unlikely
since Azure is now responsible for deleting them).
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.