Custom CI/CD variables
QEMU CI pipelines can be tuned by setting some CI environment variables.
Set variable globally in the user’s CI namespace
Variables can be set globally in the user’s CI namespace setting.
For further information about how to set these variables, please refer to:
https://docs.gitlab.com/ee/ci/variables/#add-a-cicd-variable-to-a-project
Set variable manually when pushing a branch or tag to the user’s repository
Variables can be set manually when pushing a branch or tag, using git-push command line arguments.
Example setting the QEMU_CI_EXAMPLE_VAR variable:
git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
For further information about how to set these variables, please refer to:
https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd
Here is a list of the most used variables:
QEMU_CI_AVOCADO_TESTING
By default, tests using the Avocado framework are not run automatically in the pipelines (because multiple artifacts have to be downloaded, and if these artifacts are not already cached, downloading them make the jobs reach the timeout limit). Set this variable to have the tests using the Avocado framework run automatically.
AARCH64_RUNNER_AVAILABLE
If you’ve got access to an aarch64 host that can be used as a gitlab-CI runner, you can set this variable to enable the tests that require this kind of host. The runner should be tagged with “aarch64”.
S390X_RUNNER_AVAILABLE
If you’ve got access to an IBM Z host that can be used as a gitlab-CI runner, you can set this variable to enable the tests that require this kind of host. The runner should be tagged with “s390x”.