| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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 fb5b97d0912f687b7e83836bfa52359d81c0ef76.
|
| |
|
|
|
|
|
|
|
|
| |
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 d89be7ee6e382de2517f153fb4d08136322fbdd0.
|
| |
|
|
| |
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
|
|
|
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.
|
