path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* ci: use clone instead of fetchKevin Daudt2020-02-151-1/+1
| | | | | This makes sure there is no interference from older merge requests and shallow fetches.
* ci: enable shallow cloning/fetchingKevin Daudt2020-02-101-1/+1
* ci: silence fetching from upstreamKevin Daudt2020-02-091-1/+1
| | | | To reduce noise in the job log, silence the output of `git fetch`.
* ci: fix typo in armv7 image tagKevin Daudt2019-12-301-1/+1
* ci: use armv7 image for armv7 build jobKevin Daudt2019-12-301-0/+3
| | | | | armv7 runs on an aarch64 machine, so we need to explicitly ask for the armv7 image, as well as running the shell with linux32.
* Revert "gitlab-ci: remove git fetch before_script"Kevin Daudt2019-10-191-0/+7
| | | | | | | Decided it's better to do it in one place than repeating the logic on multiple places. This reverts commit fb5b97d0912f687b7e83836bfa52359d81c0ef76.
* gitlab-ci: remove git fetch before_scriptKevin Daudt2019-10-191-6/+0
| | | | | | | | | | 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.
* gitlab-ci: override git strategy / depthKevin Daudt2019-10-191-0/+4
| | | | | | | | | 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.
* gitlab-ci: enable armv7 build jobKevin Daudt2019-10-141-0/+9
* gitlab-ci: revert "gitlab-ci: temporarily disable s390x"Kevin Daudt2019-10-141-0/+9
| | | | | | The builder is back. This reverts commit d89be7ee6e382de2517f153fb4d08136322fbdd0.
* gitlab-ci: temporarily disable s390xKevin Daudt2019-10-121-9/+0
| | | | Until the runner is back.
* gitlab-ci: add build job for aarch64Kevin Daudt2019-10-121-0/+9
* gitlab-ci: upload built packages as artifactsKevin Daudt2019-10-021-0/+16
| | | | | | | | 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.
* .gitlab-ci.yml: add ci jobs to build changed aportsKevin Daudt2019-09-241-0/+40
| | | Closes !74
* aports: enable gitlab-ci lintingKevin Daudt2019-08-151-0/+20
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.