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: 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>

VER and PATH variables need to be dynamically replaced

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

Having these headers and libraries lists in a not reproducible order
can generate random errors with abi-compliance-checker

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

When an xml descriptor file is provided, its path is not returned.
Consequently, run_abi_checker() fails due to an empty value.

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

https://phabricator.apertis.org/T8901



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

The script is split in a apertis-pull-upstream-kernel and a apertis-rebase-upstream-kernel
script.

The first one only updates the upstream/linux-* branch and the second
one does the actual rebase of the patches on the new upstream.

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

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

These scripts are separated in 2 parts:
 * Get the latest kernel and try to rebase the apertis kernel on it
 * Push the changes and create merge requests for the pristine-lfs and
   apertis/v.*-security branches

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

This value will be used to determine if the job should fail or succeed

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>

We may want to run the CI pipeline to pull updates from a debian release
backports upstream. Extend this script to handle those branches.

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>

Explicitly attempt a fast forward merge before rebasing.

Currently we always try to rebase, which already doews a fast-forward
merge when possible. The issue is that after that we incoditionally try
to append a new changelog entry and if we're fast-forwarding we should
**not** to that since the changelog will already have a version equal or
newer than the one we're trying to add.

By explicitly attempting a fast-forward merge and exiting early we avoid
that issue.

This has not been a particular issue so far since the mirroring
pipeline which uses the rebasing feature does not usually trigger it
when a fast-forward is possible and will create all the branches in
their final state.

However in some cases unrelated errors encountered during the process
have left repositories in a inconsistent state and this change allows to
recover cleanly from those situations.

Signed-off-by: Emanuele Aina <emanuele.aina@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>