diff options
| author | James E. Blair <jim@acmegating.com> | 2021-09-23 13:43:42 -0700 |
|---|---|---|
| committer | James E. Blair <jim@acmegating.com> | 2021-09-23 14:12:35 -0700 |
| commit | 025356aeda81db974ddad1512971dcf45b19d5ac (patch) | |
| tree | 00b468c4304d50259d8241e8cec91f710486e578 /tests/fixtures/layouts | |
| parent | efe6b7abc73de3d4c8a4be65c25e4c03df22f75d (diff) | |
| download | zuul-025356aeda81db974ddad1512971dcf45b19d5ac.tar.gz | |
Add a test for dequeue-on-new-patchest
This setting (which is likely rarely used) instructs Zuul not to
dequeue an item merely because it has had a new patchset uploaded.
However, if another item depends on such a change, that other item
should still be dequeued because its dependencies are out of date.
Add a test for that so that future changes to the change cache don't
inadvertently alter this behavior.
Change-Id: Ib2e8504c37644e06d0ac0608fa7c56d092e2673d
Diffstat (limited to 'tests/fixtures/layouts')
| -rw-r--r-- | tests/fixtures/layouts/no-dequeue-on-new-patchset.yaml | 49 |
1 files changed, 49 insertions, 0 deletions
diff --git a/tests/fixtures/layouts/no-dequeue-on-new-patchset.yaml b/tests/fixtures/layouts/no-dequeue-on-new-patchset.yaml new file mode 100644 index 000000000..08a134e24 --- /dev/null +++ b/tests/fixtures/layouts/no-dequeue-on-new-patchset.yaml @@ -0,0 +1,49 @@ +- pipeline: + name: check + manager: independent + dequeue-on-new-patchset: false + trigger: + gerrit: + - event: patchset-created + require: + gerrit: + approval: + - Code-Review: 2 + success: + gerrit: + Verified: 1 + failure: + gerrit: + Verified: -1 + +- job: + name: base + parent: null + run: playbooks/base.yaml + +- job: + name: project1-test + +- job: + name: project2-test + +- job: + name: project3-test + +- project: + name: org/project1 + check: + jobs: + - project1-test + +- project: + name: org/project2 + check: + jobs: + - project2-test + +- project: + name: org/project3 + check: + jobs: + - project3-test |