546ad5353a
This updates the Gerrit driver to match the pattern in the GitHub driver where instead of specifying individual trigger requirements such as "require-approvals", instead a complete ref filter (a la "requirements") can be embedded in the trigger filter. The "require-approvals" and "reject-approvals" attributes are deprecated in favor of the new approach. Additionally, all require filters in Gerrit are now available as reject filters. And finally, the Gerrit filters are updated to return FalseWithReason so that log messages are more useful, and the Github filters are updated to improve the language, avoid apostraphes for ease of grepping, and match the new Gerrit filters. Change-Id: Ia9c749f1c8e318fe01e84e52831a9d0d2c10b203
23 lines
870 B
YAML
23 lines
870 B
YAML
---
|
|
features:
|
|
- |
|
|
Gerrit pipeline triggers now support embedded require and reject
|
|
filters in order to match. Any conditions set for the pipeline in
|
|
require or reject filters may also be set for event trigger
|
|
filters.
|
|
|
|
This can be used to construct pipelines which trigger based on
|
|
certain events but only if certain other conditions are met. It
|
|
is distinct from pipeline requirements in that it only affects
|
|
items that are directly enqueued whereas pipeline requirements
|
|
affect dependencies as well.
|
|
- |
|
|
All Gerrit "requires" filters are now available as "reject"
|
|
filters as well.
|
|
deprecations:
|
|
- |
|
|
The `require-approval` and `reject-approval` Gerrit trigger
|
|
attributes are deprecated. Use :attr:`pipeline.trigger.<gerrit
|
|
source>.require` and :attr:`pipeline.trigger.<gerrit
|
|
source>.reject` instead.
|