... | ... | @@ -50,4 +50,16 @@ The web UI is deployed from a fixed version of the upstream container image. |
|
|
|
|
|
Instructions for updating the tag are in the Dockerfile: https://gitlab.gnome.org/sthursfield/openqa-ansible/-/blob/main/roles/openqa/files/Dockerfile
|
|
|
|
|
|
After updating the tag, rerun the Ansible playbook to deploy the new version. |
|
|
\ No newline at end of file |
|
|
After updating the tag, rerun the Ansible playbook to deploy the new version.
|
|
|
|
|
|
# openQA workers and gitlab-runners integration
|
|
|
OpenQA is often used with dedicated worker machines, but we wanted to avoid creating a "pet" system that would require special maintenance. So after the CI pipeline has a Gitlab runner successfully build the artifacts, it then has another runner create an openQA worker instance with a unique ID. This ID ensures it can only be used by the pipeline that created it. The runner then issues a command to the openQA UI to perform the tests on its created worker, using API key and secret values configured in the Gitlab project.
|
|
|
|
|
|
You can see how everything fits together in this MR:
|
|
|
- https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/1251/diffs
|
|
|
|
|
|
Current code implementing this at (It was moved from the original location):
|
|
|
- https://gitlab.gnome.org/GNOME/openqa-tests/-/blob/4b924e03d8e023c17cb83aef9cf3ed54ace9e75e/.gitlab-ci.yml#L24
|
|
|
- https://gitlab.gnome.org/GNOME/openqa-tests/-/tree/771c79f4076e7776f6dfbdad93435a361cfd002e/utils
|
|
|
|
|
|
|