Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

Signed-off-by: Apertis CI <devel@lists.apertis.org>

When retrieving the artifacts, pass the job token so that things work
fine even for downstreams requiring authenticated access.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Use a multiline string rather than splitting each line of a for loop
in a separate string, as it feels quite hackish and may break at
some point.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Put the lists of dev and stable branches at the top to make them easier
to customize for downstreams.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Make the downstreams' life easier by making the osname a parameter
that can be easily customized instead of hardcoding `apertis` in
multiple places.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

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

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

Building only on the main branches has some drawbacks:
* no test is run before changes are landed
* the "merge only when pipeline succeed" settings make it impossible to
  merge changes

To fix that, always build things but only publish when on the
default branch.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Keep the v2021pre and v2022dev0 branches around since we need to do
minor releases for them.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

This will help in release script automation to update the current
development release

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

By default `curl` annoyingly returns success even if it gets an HTTP
error code such as 404, leading to more confusing errors later in the
pipeline when trying to unzip HTML error pages.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Keep v2021dev3 around at least until it is released.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

gitlab-ci: Tag lightweight jobs to reduce their latency

See merge request !1

Lightweight CI runners have been introduced to run jobs which have low
resource consumption and do not need privileged containers to reduce costs
and latency, so let's use them.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

We don't have access to the git repo that contains the release
branches, for now take the easiest approach of hard coding the
branches we care about.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We are now building the pages from this repo so we don't need the
template, merge it into the main .gitlab-ci.yml file for simplicity.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Since we should now be able to use multi-project pipelines, setup the
main branch so that we can use it in a multi-project pipeline.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Rather than iterating over the available branches, checking them out
and building the pages, we are going to render the pages in a separate
jobs and pick up the artifacts created by those jobs. Tweak the
template `render-pages` in `.gitlab-ci/templates-render-pages.yml` to
retrieve and extract the artifacts rather than generating the pages.
Tweak the naming to be more consistent with its new role.

We need the tools to generate the main menu on every branch that
generates test-cases. Rather than copying the tools to them all, keep
the tools here, archive them and pull out the archive in the template
which is also stored on this branch.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We only want the update to run for apertis\ branches, restrict using a
wildcard.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We're using the gitlab CI configuration on many branches, create a
separate branch for the gitlab CI logic that can be used from the other
branches. This avoids the need to keep all the other branches in sync.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>