- 30 Jun, 2022 9 commits
-
-
Generally we're standardizing on ansible as a tool to deploy $things; Whether that's to kubernetes or otherwise. Switch CI to deploy the staging setup via the lava-server-staging playbook in the ansible core recipes. Signed-off-by:
Sjoerd Simons <sjoerd@collabora.com>
-
Paweł Wieczorek authored
This patch is intended to prevent CI pipeline flakiness caused by the changes from the container image publisher. Script environment is expected to be Alpine hence the specific base image. DinD service does not need to be bound to a specific base image. Signed-off-by:
Paweł Wieczorek <pawiecz@collabora.com>
-
With this and adjusted gitlab variables changes in staging will be published in a the staging lava repository published at: deb https://repositories.collabora.co.uk/lava/staging buster main While the production repository will still publish to the sysadmin debian repository Signed-off-by:
Sjoerd Simons <sjoerd@collabora.com>
-
-
Only deploy it from the staging branch though; As that will get an actual dispatcher attached and our development cluster isn't big enough for a lot of deployments...
-
-
For testing publishing docker images from all branches is quite useful; So make the naming be specific rather then one general name
-
The new publish stage builds only the lava-server image and publishes it to the registry.
-
This tests our containerized lava-server based on the Debian packages by firing it up, setting up a dispatcher container and a lavacli container alongside it and then: - creating a super user - adding the qemu device type and a qtest device of that type - using lavacli to set the device dictionary and health test - running a regular job - making sure both the health check and the regular job succeeded
-