summaryrefslogtreecommitdiff
path: root/1 projects/Create backup service/Testing
diff options
context:
space:
mode:
Diffstat (limited to '1 projects/Create backup service/Testing')
-rw-r--r--1 projects/Create backup service/Testing/openstack-testing.md1
-rw-r--r--1 projects/Create backup service/Testing/tempest.md0
-rw-r--r--1 projects/Create backup service/Testing/zuul.md10
3 files changed, 0 insertions, 11 deletions
diff --git a/1 projects/Create backup service/Testing/openstack-testing.md b/1 projects/Create backup service/Testing/openstack-testing.md
deleted file mode 100644
index 80d9c06..0000000
--- a/1 projects/Create backup service/Testing/openstack-testing.md
+++ /dev/null
@@ -1 +0,0 @@
-https://governance.openstack.org/tc/reference/project-testing-interface.html
diff --git a/1 projects/Create backup service/Testing/tempest.md b/1 projects/Create backup service/Testing/tempest.md
deleted file mode 100644
index e69de29..0000000
--- a/1 projects/Create backup service/Testing/tempest.md
+++ /dev/null
diff --git a/1 projects/Create backup service/Testing/zuul.md b/1 projects/Create backup service/Testing/zuul.md
deleted file mode 100644
index defdc48..0000000
--- a/1 projects/Create backup service/Testing/zuul.md
+++ /dev/null
@@ -1,10 +0,0 @@
-project gating; basically run tests on subject branch but as if it had been merged to master. It's possible that subject branch does not contain all changes that are in master and might break on those.
-
-ci system listens on code-rview events and runs tests
-nodepool, vms containers, drivers oa openstack, k8s etc
-
-pipeline; multiple projects can be associated with 1 pipeline, each of them specifies their own jobs.
-pipelines are triggered by events.
-list of triggers: https://zuul-ci.org/docs/zuul/latest/drivers/index.html#drivers
-
-reporters; report pipeline job results, different reporters exist .e.g gerrit (leaves review comment)