1e77c9c834
These originally allowed customizing the ci/Makefile script which was the core of the local container executions. The problem was that however flexible this may have been, it never mirrored what was being done as part of the GitLab jobs. Motivated by the effort of mirroring GitLab jobs locally, these would only ever make sense to be set/used in interactive shell container sessions where the developer is perfectly capable of using the right meson/ninja CLI options directly without going through another shell variable indirection as it was the case with these ci/helper options. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| buildenv | ||
| cirrus | ||
| containers | ||
| gitlab | ||
| lcitool | ||
| gitlab.yml | ||
| helper | ||
| integration-template.yml | ||
| integration.yml | ||
| jobs.sh | ||
| Makefile | ||
| manifest.yml | ||
| README.rst | ||
| util.py | ||
CI for libvirt
This document provides some information related to the CI capabilities for the libvirt project.
GitLab CI tuning
The behaviour of GitLab CI can be tuned through a number of variables which can be set at push time, or through the UI. See ci/gitlab.yml for further details.
Cirrus CI integration
libvirt currently supports three non-Linux operating systems: Windows, FreeBSD and macOS. Windows cross-builds can be prepared on Linux by using MinGW-w64, but for both FreeBSD and macOS we need to use the actual operating system, and unfortunately GitLab shared runners are currently not available for either.
To work around this limitation, we take advantage of Cirrus CI's free offering: more specifically, we use the cirrus-run script to trigger Cirrus CI jobs from GitLab CI jobs so that the workaround is almost entirely transparent to users and there's no need to constantly check two separate CI dashboards.
There is, however, some one-time setup required. If you want FreeBSD and macOS builds to happen when you push to your GitLab repository, you need to
set up a GitHub repository for the project, eg.
yourusername/libvirt. This repository needs to exist for cirrus-run to work, but it doesn't need to be kept up to date, so you can create it and then forget about it;enable the Cirrus CI GitHub app for your GitHub account;
sign up for Cirrus CI. It's enough to log into the website using your GitHub account;
grab an API token from the Cirrus CI settings page;
it may be necessary to push an empty
.cirrus.ymlfile to your github fork for Cirrus CI to properly recognize the project. You can check whether Cirrus CI knows about your project by navigating to:https://cirrus-ci.com/yourusername/libvirtin the CI/CD / Variables section of the settings page for your GitLab repository, create two new variables:
CIRRUS_GITHUB_REPO, containing the name of the GitHub repository created earlier, eg.yourusername/libvirt;CIRRUS_API_TOKEN, containing the Cirrus CI API token generated earlier. This variable must be marked as Masked, because anyone with knowledge of it can impersonate you as far as Cirrus CI is concerned.
Neither of these variables should be marked as Protected, because in general you'll want to be able to trigger Cirrus CI builds from non-protected branches.
Once this one-time setup is complete, you can just keep pushing to your GitLab repository as usual and you'll automatically get the additional CI coverage.
Coverity scan integration
This will be used only by the main repository for master branch by running scheduled pipeline in GitLab.
The service is proved by Coverity Scan and requires that the project is registered there to get free coverity analysis which we already have for libvirt project.
To run the coverity job it requires two new variables:
COVERITY_SCAN_PROJECT_NAME, containing the libvirt project name.COVERITY_SCAN_TOKEN, token visible to admins of libvirt project