summaryrefslogtreecommitdiff
path: root/.trash/Testing
diff options
context:
space:
mode:
authorJasper Ras <jras@hostnet.nl>2025-01-13 13:16:06 +0100
committerJasper Ras <jras@hostnet.nl>2025-01-13 13:16:06 +0100
commit9232b8d817d4cd4122947375156fa2fa1e9fba14 (patch)
treee4feb77f2e508f008b78f722e91488bb9a3f3806 /.trash/Testing
parented0753ad224f0c65133bd7a63180257eecd9f5e3 (diff)
vault backup: 2025-01-13 13:16:06
Diffstat (limited to '.trash/Testing')
-rw-r--r--.trash/Testing/Openstack testing.md5
-rw-r--r--.trash/Testing/Zuul.md15
2 files changed, 20 insertions, 0 deletions
diff --git a/.trash/Testing/Openstack testing.md b/.trash/Testing/Openstack testing.md
new file mode 100644
index 0000000..3a3db75
--- /dev/null
+++ b/.trash/Testing/Openstack testing.md
@@ -0,0 +1,5 @@
+#openstack #testing
+
+https://governance.openstack.org/tc/reference/project-testing-interface.html
+
+---
diff --git a/.trash/Testing/Zuul.md b/.trash/Testing/Zuul.md
new file mode 100644
index 0000000..f32daa3
--- /dev/null
+++ b/.trash/Testing/Zuul.md
@@ -0,0 +1,15 @@
+#openstack #ci #testing
+
+ https://zuul-ci.org/docs
+
+---
+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)