Due to a bug in abi-compliance-checker, std headers are occasionally
used for analyzing leading to wrongly detect an ABI breakage.
We globally exclude them to avoid this noise until it is fixed in ACC.

See: https://github.com/lvc/abi-compliance-checker/issues/85



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

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

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

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

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

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

The call of the abi-compliance-checker might fail due to
errors. Possible reasons are the failed compilation of the
header files. To ease the analysis of the job logs the
additional printout might help.
Correct 'apt update' command.

Signed-off-by: Tino Lippold <Tino.Lippold@de.bosch.com>

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

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

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

https://phabricator.apertis.org/T8901



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

Detlev Casanova authored 2 years ago and Ariel D'Alessandro committed 2 years ago

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

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

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

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

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Updates available in -security and -proposed-updates fall into the main Debian repository
after a Debian release point. In case an update has been imported from -security or -proposed-updates,
our main Debian branch stays out of date. Consequently, the Dashboard wrongly complains about an
available update from Debian.

In this scenario, the main Debian branch needs to be synchronized with the
-security or -proposed-updates branch used previously.

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

These being essential packages, a script is needed to backup binaries
used to do the upgrade.

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

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

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

gitlab-rulez package is now required to run import-debian-package tests.
Let's test this script on apertis, as it provides the package.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

To import a new package from Debian the current process required several
manual steps. This commit adds the --push-remote option to allow
creating and pushing the imported package to apertis remote gitlab
instance.

The following steps are now automatized:
* package folder is created and import process is performed in there.
* remote repo is created if it doesn't exist.
* remote branches and tags are pushed.
* gitlab settings are applied to remote repo.
* CI pipeline is triggered on all downstream branches.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

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

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Import GitLabCI tests from `infrastructure/packaging-tools`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

As this tool is now provided as a development package we can depend on it.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Update apt repositories before call build-dep.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

These tools are moved from
`infrastructure/apertis-docker-images/package-source-builder`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

This tool is moved from `infrastructure/packaging-tools`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

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

By default pipelines do not run in Merge Request context, but that's
exactly what the parent ci-package-builder pipeline is now doing.

Add a rule to run the local pipeline in whatever context the parent
pipeline triggered it.

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

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

Demote dependency on ribchester to a suggests since we no longer ship
the Canterbury appfw on the Bullseye based v2022dev2.

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

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

Add some rules to the local pipeline so it gets skipped when tags are
pushed, instead of creating jobs that are currently failing.

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

Apertis has moved to using external references in the CI config path setting
for the packagign repositories, so the gitlab-ci.yml embedded in the
repository is no longer needed.

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

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

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