Merge "Temporarily remove pending release notes in order to merge 3.19.1"
This commit is contained in:
commit
b53cacb121
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
The action "promote" is now available via the tenant-scoped REST API using
|
||||
the zuul cli.
|
|
@ -1,4 +0,0 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Support for Ansible 2.7 has been removed.
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Builds in the SQL reporter have a "held" attribute set to True if the build
|
||||
triggered a autohold request. Builds can be filtered by held status.
|
||||
upgrade:
|
||||
- |
|
||||
If using a SQL reporter, the zuul_builds table will be updated with a new
|
||||
'held' column. The `zuul-scheduler` and `zuul-web` services need to be restarted
|
||||
together for the change to take effect.
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Previously the SqlReporter would record the job name in the database in
|
||||
place of the url if the url was empty. This has now been updated to store
|
||||
a null in the database for that case. Zuul will automatically run a
|
||||
database migration to correct old values.
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Subdirectories of ``zuul.d`` or ``.zuul.d`` can be ignored when
|
||||
reading configuration by placing a ``.zuul.ignore`` file inside
|
||||
them.
|
|
@ -1,4 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
The ``find`` module is now allowed to run on the executor.
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Changes can now be dequeued via the Github checks API. If a github
|
||||
reporter is configured to use the checks API, all running checks will
|
||||
provide a custom "Abort" action.
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Zuul now respects GitHub review requirements when enqueuing into gate
|
||||
pipelines. This works for github.com and GitHub Enterprise starting with
|
||||
version 2.21.0.
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- Jobs may specify the new ``intermediate`` flag to note they may only
|
||||
be inherited by abstract jobs. This can be useful if building a job
|
||||
hierarchy where wish to limit where a base job is instantiated.
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Although the documentation states that the MQTT reporter reports the build's
|
||||
log_url, this was only true as long as :attr:`tenant.report-build-page` was
|
||||
disabled. As soon as the setting was enabled, the MQTT reporter reported the
|
||||
url to the build's result page in Zuul. As MQTT is meant to be consumed by
|
||||
machines, this broke use cases like log post processing.
|
||||
|
||||
This was fixed so that the :attr:`<mqtt schema>.buildset.builds.log_url` now
|
||||
always contains the log url, while an additional field
|
||||
:attr:`<mqtt schema>.buildset.builds.web_url` contains the url to the
|
||||
build's result page if :attr:`tenant.report-build-page` is enabled.
|
|
@ -1,9 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
The builds/ and buildset/ API endpoints now include information about
|
||||
retried builds. They are called non-final as those are all builds that
|
||||
were retried at least once and thus weren't visible to the user so far.
|
||||
|
||||
The builds/ API can filter those retried builds and you might exclude
|
||||
them from API result by setting ``final=false`` in the API request.
|
|
@ -1,4 +0,0 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
Support for running Zuul under Python 3.5 has been dropped.
|
|
@ -1,17 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
An option to use the URL of the Zuul build page when reporting has
|
||||
been added. This fetaure requires that all the pipelines in the
|
||||
tenant have a :ref:`SQL reporter<sql_reporter>` configured, and at
|
||||
least one of :attr:`tenant.web-root` or :attr:`web.root` must be
|
||||
defined.
|
||||
|
||||
See :attr:`tenant.report-build-page`.
|
||||
upgrade:
|
||||
- |
|
||||
As further integration with the web interface is planned, the
|
||||
:attr:`web.root` setting in ``zuul.conf`` is marked required and
|
||||
future releases may error if it is missing. Please add it to your
|
||||
configuration now. See :attr:`tenant.web-root` for additional
|
||||
information about whitelabel tenants.
|
|
@ -1,11 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
REST API: authorizations: add a tenant-scoped endpoint at
|
||||
'/api/tenant/{tenant}/authorizations'. Calling the endpoint will return
|
||||
a list of admin tenants limited to the scoped tenant, if the user has admin
|
||||
privileges on it.
|
||||
deprecations:
|
||||
- |
|
||||
REST API: authorizations: the /api/user/authorizations endpoint is deprecated
|
||||
in favor of the tenant-scoped endpoint. It will be removed next release.
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Host key checking is now disabled for a host in the generated
|
||||
Ansible inventory if ``host-key-checking`` is set to ``False``
|
||||
in the corresponding nodepool config.
|
Loading…
Reference in New Issue