path: root/.gitlab-ci.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-06-22gitlab CI: add Arch to the list of built imageswip/archPeter Hutterer1-0/+65
Signed-off-by: Peter Hutterer <>
2018-06-22gitlab CI: add pkgconfig to the listPeter Hutterer1-2/+2
It's pulled in by some dependency anyway, but for the sake of being explicit, pull it in. Signed-off-by: Peter Hutterer <>
2018-06-21gitlab CI: run ninja test tooPeter Hutterer1-0/+8
Fixes Signed-off-by: Peter Hutterer <>
2018-06-19CI: WIP: attempt to clean up the registry before leavingBenjamin Tissoires1-12/+116
According to multiple sources, referenced in The garbage collector of the registry won't clean up docker images that still have blob references. We should clean up the manifests instead of simply overwriting the tag. Note: this requires to set up a personal token with api access from the maintainers in the form of (for instance): "PERSONAL_TOKEN_bentiss" Reviewed-by: Peter Hutterer <> Signed-off-by: Benjamin Tissoires <>
2018-06-19CI: speed up the docker_check stageBenjamin Tissoires1-4/+4
There is no point in login in to the registry if there is no need to create a new docker image. Reviewed-by: Peter Hutterer <> Signed-off-by: Benjamin Tissoires <>
2018-06-19CI: do not pull images when checking for the creation dateBenjamin Tissoires1-4/+30
Reviewed-by: Peter Hutterer <> Signed-off-by: Benjamin Tissoires <>
2018-06-19doc: point to the gitlab ci file for a list of required packagesPeter Hutterer1-2/+13
Signed-off-by: Peter Hutterer <>
2018-06-18gitlab ci: use GIT_DEPTH of 1Peter Hutterer1-0/+1
We don't need the full repo Signed-off-by: Peter Hutterer <>
2018-06-18CI: Hook up GitLab CIBenjamin Tissoires1-0/+406
The main tasks it does is build on a few different distros as well as build with the various build options to make sure they work.It doesn't (yet) run the test suite runner because that one mostly requires device nodes to operate on. Most of the fancy is to get the docker images ready. A dnf update takes forever, so we don't want to do that on 10 different machines. So instead we build docker images with all the bits pre-installed, push that to the registry and use those images for testing. To speed things up, we only do that when the current image is older than a week. And we only do that when we push to libinput proper, so a merge request or pushing to your private gitlab repo will never trigger a docker image update - it will trigger the tests and use the docker images tough. Co-authored-by: Peter Hutterer <> Signed-off-by: Benjamin Tissoires <>