Commit 627b99df authored by Peter Hutterer's avatar Peter Hutterer
Browse files

doc: add a short description of how things fit together

Can be extended over time but it's better to have something than nothing.
Signed-off-by: Peter Hutterer's avatarPeter Hutterer <>
parent a2d54aad
Pipeline #272471 passed with stages
in 1 minute and 41 seconds
.. _templates:
Hacking on the CI Templates
This is an outline of how everything fits together in this repository.
This repository contains both the source **and** the generated
output. The directory structure is as follows:
- ``bootstrap``: Scripts used by the bootstrap images.
- ``src``: The source template files and per-distribution configuration.
- ``templates``: The **generated** templates. Do not edit.
- ``test``: Scripts used by the CI to test images.
- ``tools``: The :ref:`ci-fairy <ci-fairy>` tool.
The ``ci-templates`` repository has two consumables:
- the files in the ``templates`` folder are to be included by external
projects, see :ref:`templates` for the details.
- the CI pipeline produces several container images that these templates
rely on. These images are hardcoded in the templates and are the ones used
to build the real jobs in the external project. Some of these images are
mirrored to to reduce bandwidth requirements on our
When templates change, the ``src/`` script generates
both the resulting ``templates/`` **and** the ``.gitlab-ci.yml`` file that
generates the consumable images and the various CI pipelines to test these
images and the templates.
The consumable images are built in the ``bootstrap`` phase of the CI
pipeline, see the ``.gitlab-ci/bootstrap-ci.yml`` file for details.
As a short summary: this stage builds container images that are capable of
building the images the external projects need.
......@@ -11,6 +11,7 @@ efficiently use the Gitlab CI on
Indices and tables
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment