Dockerize package builds

Switch package builds to use containerized docker environment.
With dockerized builds:
* build dependnecies can be simply updated by updating (and regenerating)
  the docker image files
* Resources are controlled in a more deterministic order

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.co.uk>

packaging/apertis-build-package.yaml

@@ -18,7 +18,7 @@
         These jobs are for packages where Apertis is the upstream
         developer. See <https://gitlab.apertis.org/>.
     project-imagetype: freestyle
-    node: apertis-development
+    node: docker-slave
     properties:
       - inject:
           properties-content: |
@@ -52,6 +52,10 @@
           - file:
               credential-id: '{osc-credentials-id}'
               variable: OSCRC
+      - docker-custom-build-env:
+          image-type: 'pull'
+          image: docker-registry.apertis.org/apertis/apertis-{distro}-package-builder
+          force-pull: true
     triggers:
       - pollscm:
           cron: "H/5 * * * *"

packaging/apertis-build-packaging.yaml

@@ -19,7 +19,7 @@
         is done outside Apertis, with the Apertis packaging adding OS integration
         and local modifications. See <https://gitlab.apertis.org/packaging/>.
     project-imagetype: freestyle
-    node: apertis-development
+    node: docker-slave
     properties:
       - inject:
           properties-content: |
@@ -54,6 +54,10 @@
           - file:
               credential-id: '{osc-credentials-id}'
               variable: OSCRC
+      - docker-custom-build-env:
+          image-type: 'pull'
+          image: docker-registry.apertis.org/apertis/apertis-{distro}-package-builder
+          force-pull: true
     triggers:
       - pollscm:
           cron: "H/5 * * * *"