`only` has been deprecated and gitlab recommends to use rules instead,
which are more flexible.

Add a global workflow and change the `only` specifications to `rules`.

This ci job will trigger a downstream multi-project pipeline to
build a disk image.

The builder is available again.

This reverts commit 9a738fc3.

The CI hosts will not be available for a couple of days. Disable the
jobs to keep the pipelines going.

Jakub Jirutka authored 2 years ago and alice committed 2 years ago

This job is not started automatically as others, but the
developer/contributor can start it via GitLab UI.

This is now done directly by the lint script

Due to recent changes in git, the owner of the repository files matter.
In CI, the repository is cloned by root, while the CI jobs run as a
non-root user. This causes git to fail with an error message.

This was already fixed in the ci build script, but the `before_script`
is run before that, and now starts to fail because the updated git
version is part of the image itself.

Because we fetch the commits in the build script anyway, lets just
remove the before_script.

This reverts commit f24197dc.

This is now handled by the build script itself so that it's able to skip
this step in case the size is larger than the limit.

This makes sure there is no interference from older merge requests and
shallow fetches.

To reduce noise in the job log, silence the output of `git fetch`.

armv7 runs on an aarch64 machine, so we need to explicitly ask for the
armv7 image, as well as running the shell with linux32.

Decided it's better to do it in one place than repeating the logic on
multiple places.

This reverts commit fb5b97d0.

To know what aports are changed in a merge request, we need to know
where the target branch is, so that we can use git diff against that
branch.

To test this, this was added in the CI jobs description in a global
`before_script`, but this is now being handled by respective scripts
themselves, so the before_script is now redundant.

In order to properly calculate what aports have been changed, we need
proper history being present. A shallow clone interferese with that.

Instead of having to override these settings on each project (forks of
aports), we can override these settings in the CI jobs description
instead.

The builder is back.

This reverts commit d89be7ee.

Until the runner is back.

gitlab allows us to define artifacts that will be uploaded to gitlab and
available to download for some time.

Specify that the built packages should be uploaded to gitlab, along with
the public key.

Closes !74

Kevin Daudt authored 5 years ago and Natanael Copa committed 5 years ago

This will enable the CI linting job for merge requests done on gitlab.
The linting job will allow for failures, so linting failures will show
up as worning, but won't prevent the rest of the CI pipeline to
continue.