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: Walter Lozano <walter.lozano@collabora.com>

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>

During the rebase on bookworm, the image used was updated to
Ubuntu 23.04 (0850575e) which is a non LTS version and will be EOL
at the end of January 2024. Instead, use Bookworm which is supported
until 2028 (LTS).

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

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>

By default Gitlab will use the artifacts of all the previous stages,
causing the archive created at the pack stage to include unneeded
files. This creates confusion and increases the size of the tarball.

To overcome this issue, specify which are the artifacts we are interested.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

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

aarch64-linux-gnu-gcc-12 relies on symbols from GLIBC_2.36
which is only available since Ubuntu 22.10 but it's not a
LTS release, let's use Ubuntu LTS 23.04 instead.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

After the rebase on top of Bookworm switch to gcc-12.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

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: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

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

Drop non required builddeps to avoid dependency issues.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Bullseye and thus v2022 ship with GCC 10.

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

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

The `upload.sh` script uses `etc/os-release` to figure out what is the
current Apertis release channel (for instance, v2021) and computes the
upload destination accordingly.

Unfortunately it is currently set up to run in a Ubuntu 16.06 Xenial
container, which means that uploads end up in places like
`/srv/images/public/daily/xenial/20201215.173/toolchain/`.

Switch the container image so that things work correctly.

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

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

The default timeout has been set to 2h in the project settings, but only
the libc jobs really need more than the standard 1h.

Set the non-standard timeout only the jobs that really need it so we can
later drop the custom setting.

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

Also make it easier to customize.

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

The package-builder image is a multi-gigabytes image with a bunch of random
packages pre-installed. It originated as a replacement for the specially
configured Jenkins workers used in the past to build a very restricted set of
packages and it is specifically tailored to ship all their build-dep out of the
box as the Jenkins jobs ran as unprivileged users so they could not install
them on their own.

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

We generate logs that exceed the GitLab limits, so we also capture them
as artifacts. However, so far we didn't capture errors, which turn out
to be quite important when debugging issues.

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

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

Emanuele Aina authored 5 years ago and Peter Senna Tschudin committed 5 years ago

Rather than building gcc, binutils, gdb and libc in a single, sequential
job, build them in separate, parallel jobs.

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

Emanuele Aina authored 5 years ago and Peter Senna Tschudin committed 5 years ago

Move common stuff to `before_script:` and `after_script:` to make it
easier to split each step into its own job.

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

Emanuele Aina authored 5 years ago and Peter Senna Tschudin committed 5 years ago

To secure repeatability, check out a specific commit from the
glibc_version_header repository. Ideally we'd like to check out a tagged
release, but the only release at the moment is 0.1 and is quite
outdated, so let's pick the current master.

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

Emanuele Aina authored 5 years ago and Peter Senna Tschudin committed 5 years ago

Prepare for splitting each step of the build in multiple stages by
lifting the code of the global script in the pipeline defintion itself
to be able to refactor it later.

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

Do not repeat the instructions for each architecture, but use templates to be
instantiated for each architecture.

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