summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* gitlab CI: drop Fedora 30Peter Hutterer2020-08-201-33/+0
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: build an rpm package to verify the installed file listPeter Hutterer2020-07-221-6/+30
| | | | | | | | | | | | | | | | | This is not a package intended for, it's a job to fail when we accidentally change the file list. An rpmbuild job like this was what detected f15da0f10890467712222410233c0bec9faefdd0. The spec file resembles the Fedora one but has BuildRequires removed (we rely on the container for that). The same task could be achieved by keeping a file list and comparing the installed tree but since I had the rpm spec file already, let's use that for now. This requires meson 0.55 which hit F32 yesterday. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: hook up coverityPeter Hutterer2020-07-031-0/+43
| | | | | | | | | | | | | | | | | This requires the COVERITY_SCAN_TOKEN as listed on the project settings page in coverity itself. The intention here is to run this as a scheduled job, with the pipeline schedule itself controlling the branch name etc. This way we can keep the gitlab CI simple enough and just check for COVERITY_SCAN_TOKEN itself. This job shouldn't ever fail unless coverity is down (we'll fix that then), the results of the coverity run are sent to the user that owns the the scheduled pipeline, i.e. me. Because coverity does not currently work on F32 (invalid GNU version number: 101), we force this to run on F31. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: drop custom scheduled handling, set FDO_FORCE_REBUILD insteadPeter Hutterer2020-07-031-19/+5
| | | | | | | | This is a leftover from pre-ci-templates days. Now that ci-templates handles FDO_FORCE_REBUILD remove the custom handling and for the weekly rebuild just set that variable to 1 in the scheduled pipeline itself. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: move the MR check to the deploy stagePeter Hutterer2020-06-301-1/+1
| | | | | | | | This gives the developer enough time to file an MR after pushing a branch. Having this run in the first stage means we get false positives because no MR has been filed yet when the job is run. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: check merge requests for the allow collaboration checkboxPeter Hutterer2020-06-151-0/+18
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: use ci-fairy for commit message checksPeter Hutterer2020-06-151-7/+2
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: alpine needs pip explicitly installed nowPeter Hutterer2020-06-031-3/+3
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: Ubuntu 19.04 is EOL, drop itPeter Hutterer2020-04-181-34/+0
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab ci: fix a templating whitespace issuePeter Hutterer2020-04-161-1/+0
| | | | | | | | For some reason I'm too tired to investigate, the whitespace in the CI is different than the locally generated one. Alpine must've updated something, I guess. Quickfix it by adjusting the whitespace so it's correct again. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: switch the 'needs' tags to a dashed listPeter Hutterer2020-03-231-10/+20
| | | | | | We don't use the [...] style list elsewhere, so let's not do this here either. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: update the various build tests to F32Peter Hutterer2020-03-231-26/+59
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* ci: move the ci template to the expected file for ci-fairyBenjamin Tissoires2020-03-181-1/+1
| | | | | | this makes the command to type much easier Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
* ci: use ci-fairy to generate the template, not a custom scriptBenjamin Tissoires2020-03-181-2/+9
| | | | Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
* ci: use the ci fairy to delete unwanted tagsBenjamin Tissoires2020-03-181-64/+13
| | | | | | here is some magic dust from https://gitlab.freedesktop.org/libevdev/libevdev/-/merge_requests/49/diffs?commit_id=325839e6401d322ed632bf30e2e0255785bb31f6#7bc093350962b0f3fe1e612f06beaba806ee061f_219_217 Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
* ci: use latest templates, and APIBenjamin Tissoires2020-03-181-111/+125
| | | | Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
* tools: switch tool option parsing test to use pytestPeter Hutterer2020-03-171-8/+8
| | | | | | | | pytest is more powerful than unittest, so let's switch to that instead. And in the process fix a few tests that for some reason succeeded even though they shouldn't have (e.g. the autorestart test). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: drop the distribution "flavor" in favor of using the namePeter Hutterer2020-02-261-15/+15
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: split the task to run on a VM out from the host systemPeter Hutterer2020-02-261-3/+9
| | | | | | No functional changes here, it just makes the actual task more generic Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: drop the distro name from the VM jobsPeter Hutterer2020-02-261-30/+30
| | | | | | | | This changes rarely and it doesn't carry a lot of information anyway, at least compared to the jobs that are specifically designed to build on various distributions. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: update to latest ci-templatesPeter Hutterer2020-02-241-9/+9
| | | | | | | Removes the special distro "flavor" handling for arch and it gives us nicer warnings for VM failures. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: run the kvm test suite without libwacomPeter Hutterer2020-02-241-0/+36
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: pass the MESON_ARGS through to the VM as wellPeter Hutterer2020-02-241-0/+1
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: mark the template file as yaml file for vimPeter Hutterer2020-02-241-1/+1
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: don't run meson test on the scan-build jobPeter Hutterer2020-02-241-0/+1
| | | | | | | | | | | Unfortunate side-effect of this: scan-build would store the logs in the build dir, only for them to be immediately wiped by meson test. And that never generated the scan-build warnings. So this job was complaining about (minor) issues for a while, they just never made it to the GUI as CI failures. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: don't push to wayland web on scheduled jobsPeter Hutterer2020-02-241-0/+3
| | | | | | | | | We have a set of scheduled jobs to rebuild images and clean out old containers, but since they're largely unsupervised (i.e. not in response to a MR) we don't want to update the official documentation - just in case something goes wrong. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: rename the custom build jobsPeter Hutterer2020-02-201-41/+16
| | | | | | | | | The distro we're running on is a side-effect, it's more important to see the bit that describes what the job actually does. And while we're there, shuffle the hierarchy a bit for less duplication. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: don't hard-code the arch/alpine versionsPeter Hutterer2020-02-201-2/+2
| | | | | | | | We only have one each and they're not really versions anyway but now that it is all generated through templates, let's be consistent with the rest of the CI script. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: generate the various default-builds through templatingPeter Hutterer2020-02-201-48/+42
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: generate the VM tests through the templates as wellPeter Hutterer2020-02-201-2/+2
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: generate the CI script from a templatePeter Hutterer2020-02-201-12/+31
| | | | | | | All the distro-specific stuff is the same template anyway, so let's generate this (like we already do in libevdev and the ci-templates). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: add a comment to explain one of the jobsPeter Hutterer2020-02-201-0/+3
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: whitespace fixes for better visual alignmentsPeter Hutterer2020-02-201-12/+12
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: handling killing the qemu process betterPeter Hutterer2020-02-191-6/+1
| | | | | | | | | | | If qemu has already shut down by the time we call kill, pgrep returns nothing and we fail the script. Let's not do that. And let's replace kill pgrep with just pkill in the process. Let's get rid of the after_script part too, gitlab kills any process started in the main script anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: print a warning when our VM startup failsPeter Hutterer2020-02-191-1/+1
| | | | | | | This happens on packet-3 and packet-4 atm, so let's print out a clear warning that whatever the failure is, it's not directly related to libinput. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: retry the VM jobs on script failurePeter Hutterer2020-01-201-0/+3
| | | | | | | | | Unfortunately the various VM jobs are timing sensitive and create a bunch of false positives if the runners are under load and miss out on some of the events (the tablet proximity handling is a particularly bad test here). Let's retry on failure first to give the CI more opportunity to maybe succeed. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: update to latest ci-templatesPeter Hutterer2019-12-121-7/+7
| | | | | | Rebuild all the images to make sure this still works fine. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: fix skopeo copyPeter Hutterer2019-12-111-3/+6
| | | | | | | | skopeo doesn't handle the destination credentials correctly See ci-templates commit 0a9bdd33a98f05af6761ab118b5074952242aab0 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: use a minimal alpine image for the commit checksPeter Hutterer2019-12-111-2/+3
| | | | | | | | This runs at the same time as the other images being created so it'll fail if the image itself doesn't exist yet. Since we only need pip here, let's use alpine and install the two packages we need. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: run the meson script for the VMs as wellPeter Hutterer2019-11-281-7/+9
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: move the build instructions into a bash filePeter Hutterer2019-11-281-19/+2
| | | | | | | | | | | Extending/debugging scripts in the gitlab CI directly is a pain, the turnaround cycle is terrible. Let's move this into a shellscript that we can just call directly. Bonus side-effect: if we wanted to extend the script: set somewhere, this is now much easier to override. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: add meson to junit scriptPeter Hutterer2019-11-281-4/+12
| | | | | | | | | | | | | | This script was written by Emmanuele Bassi, copied from https://gist.github.com/ebassi/e5296ec77ae9e0d3a33fd483b5613b09/ It converts meson test results into a junit file which we can then use to display in the merge request GUI. Note that as litest writes out junit files as well, some tests are reported twice. Specifically: where litest fails the failure will be reported once through litest itself and once by meson test. Oh well. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* test: write our test case results out as junit xml filesPeter Hutterer2019-11-281-0/+3
| | | | | | | | | | | | | | | | | libcheck has the ability to write out XML files for test results, but converting those into junit isn't ideal, for a number of reasons: - junit xml is different to libcheck's xml, so not all data is available or useful. Especially with our litest wrappers around it. - litest forking off tests means we have to wrap around everything anyway to avoid multiple forks writing to the same test file. This is the minimal implementation since it's only user is likely the CI which we control fairly tightly. So there are a few corners we can skip: - no filename validation is performed by litest - we write out a lot of junit xml files (one per litest fork). Rather than collating those we just rely on the CI to find the files. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: apply some basic validity checks on the commit messagesPeter Hutterer2019-11-281-0/+21
| | | | | | | | | | | | | | Let's stop merge requests from users that don't set their git author name and email address. Aside from it looking stange in the history it'll also make it virtually impossible to ever find that user again should something important arise in the future - especially if we switch off gitlab. The rest is basic style, short subject lines, Signed-off-by lines and correct formatting. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> [bentiss: use /usr/bin/env python3 as requested by the CI] Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
* gitlab CI: rename the container_prep state to just "prep"Peter Hutterer2019-11-281-10/+10
| | | | | | So we can shove other stuff in there without it looking strange. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: use multiple extends for the default artifact/build snippetsPeter Hutterer2019-11-281-4/+4
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: use multiple extends over anchors for the upstream pullPeter Hutterer2019-11-281-9/+9
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: add a global policy snippet for retries and interruptiblePeter Hutterer2019-11-281-1/+24
| | | | | | | We want to retry if we have a system/timeout/stuck failure. And our jobs are all interruptible, we want to cancel them when the branch has new commits. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: split all extends into multiple linesPeter Hutterer2019-11-281-52/+104
| | | | | | | No functional changes, this merely prepares the file for easier multiple extends. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: work around collapsed multiline commands in the rebuild checkPeter Hutterer2019-11-051-11/+8
| | | | | | | | | Multiline commands are currently collapsed with no way of uncollapsing them (https://gitlab.com/gitlab-org/gitlab-runner/issues/3392), so we never see the skopeo invocations. Work around this by touching a file when scheduled and using that to break up the conditions. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
View Lorry Controller Status