81d84e7c15
This adds a query for changes which are set (by Gerrit) to be submitted together due to submitWholeTopic being enabled. In this case, changes which are of the same topic will be merged simultaneously by Gerrit, therefore Zuul should treat them as a set of circular dependencies. The behavior is automatic, since Gerrit will return a set of changes if the setting is enabled, or the empty list if it is not. Zuul still requires that circular dependencies be enabled in any queues where they appear. If users have submitWholeTopic enabled in Gerrit but do not have allow-circular-dependencies enabled, they may begin to see errors. However, the errors are self-explanatory, and installations such as these are already not testing what Gerrit will merge, so reporting the discrepancy is an improvement. Change-Id: Icf65913a049a9b9ddbedd20cc73bf44ffcc831b8
21 lines
868 B
YAML
21 lines
868 B
YAML
---
|
|
features:
|
|
- |
|
|
Zuul now matches Gerrit's behavior when
|
|
``change.submitWholeTopic`` is set in Gerrit.
|
|
|
|
When this setting is enabled in Gerrit and a change is submitted
|
|
(merged), all changes with the same topic are submitted
|
|
simultaneously. Zuul will now query for changes which are set to
|
|
be submitted together by Gerrit when enqueing them and treat them
|
|
as if they are a set of circular dependencies.
|
|
|
|
If the projects are not part of pipeline queues which are
|
|
configured to allow circular dependencies, then Zuul will report
|
|
failure on enqueue. Be sure that the submitWholeTopic setting in
|
|
Gerrit and the allow-circular-dependencies setting in Zuul match.
|
|
|
|
This functionality requires an HTTP connection to Gerrit. If only
|
|
an SSH connection is available, then changes submitted together
|
|
will be ignored.
|