summaryrefslogtreecommitdiff
path: root/1 projects/Create backup service
diff options
context:
space:
mode:
Diffstat (limited to '1 projects/Create backup service')
-rw-r--r--1 projects/Create backup service/Packaging/Pybuild.md8
-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
4 files changed, 19 insertions, 0 deletions
diff --git a/1 projects/Create backup service/Packaging/Pybuild.md b/1 projects/Create backup service/Packaging/Pybuild.md
new file mode 100644
index 0000000..226a53c
--- /dev/null
+++ b/1 projects/Create backup service/Packaging/Pybuild.md
@@ -0,0 +1,8 @@
+https://salsa.debian.org/python-team/tools/dh-python/-/blob/master/pybuild.rst
+^ documentation
+
+dh-python
+
+https://salsa.debian.org/python-team/packages/hatchling/-/blob/debian/latest/debian/control?ref_type=heads
+
+That shows that we can specify `pybuild-plugin-pyproject`. \ No newline at end of file
diff --git a/1 projects/Create backup service/Testing/openstack-testing.md b/1 projects/Create backup service/Testing/openstack-testing.md
new file mode 100644
index 0000000..80d9c06
--- /dev/null
+++ b/1 projects/Create backup service/Testing/openstack-testing.md
@@ -0,0 +1 @@
+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
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/1 projects/Create backup service/Testing/tempest.md
diff --git a/1 projects/Create backup service/Testing/zuul.md b/1 projects/Create backup service/Testing/zuul.md
new file mode 100644
index 0000000..defdc48
--- /dev/null
+++ b/1 projects/Create backup service/Testing/zuul.md
@@ -0,0 +1,10 @@
+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)