Skip to content

Commit 9ada9fd

Browse files
philmdhuth
authored andcommitted
docs: Document GitLab custom CI/CD variables
We introduced the QEMU_CI_AVOCADO_TESTING variable in commit f56bf4c ("gitlab: Run Avocado tests manually (except mainstream CI)"), but forgot to document it properly. Do it now. Suggested-by: Thomas Huth <[email protected]> Signed-off-by: Philippe Mathieu-Daudé <[email protected]> Reviewed-by: Daniel P. Berrangé <[email protected]> Reviewed-by: Willian Rampazzo <[email protected]> Reviewed-by: Thomas Huth <[email protected]> Message-Id: <[email protected]> Signed-off-by: Thomas Huth <[email protected]>
1 parent 69ea12b commit 9ada9fd

File tree

2 files changed

+42
-17
lines changed

2 files changed

+42
-17
lines changed

.gitlab-ci.yml

+2-17
Original file line numberDiff line numberDiff line change
@@ -16,24 +16,9 @@
1616
# QEMU CI jobs are based on templates. Some templates provide
1717
# user-configurable options, modifiable via configuration variables.
1818
#
19-
# These variables can be set globally in the user's CI namespace
20-
# setting:
21-
# https://docs.gitlab.com/ee/ci/variables/#create-a-custom-variable-in-the-ui
22-
# or set manually each time a branch/tag is pushed, as a git-push
23-
# command line argument:
24-
# https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd
19+
# See https://qemu-project.gitlab.io/qemu/devel/ci.html#custom-ci-cd-variables
20+
# for more information.
2521
#
26-
# Example setting the QEMU_CI_EXAMPLE_VAR variable:
27-
#
28-
# git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
29-
#
30-
# ----------------------------------------------------------------------
31-
#
32-
# List of environment variables that can be use to modify the set
33-
# of jobs selected:
34-
#
35-
# - QEMU_CI_AVOCADO_TESTING
36-
# If set, tests using the Avocado framework will be run
3722

3823
include:
3924
- local: '/.gitlab-ci.d/qemu-project.yml'

docs/devel/ci.rst

+40
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,46 @@ found at::
88

99
https://wiki.qemu.org/Testing/CI
1010

11+
Custom CI/CD variables
12+
======================
13+
14+
QEMU CI pipelines can be tuned by setting some CI environment variables.
15+
16+
Set variable globally in the user's CI namespace
17+
------------------------------------------------
18+
19+
Variables can be set globally in the user's CI namespace setting.
20+
21+
For further information about how to set these variables, please refer to::
22+
23+
https://docs.gitlab.com/ee/ci/variables/#add-a-cicd-variable-to-a-project
24+
25+
Set variable manually when pushing a branch or tag to the user's repository
26+
---------------------------------------------------------------------------
27+
28+
Variables can be set manually when pushing a branch or tag, using
29+
git-push command line arguments.
30+
31+
Example setting the QEMU_CI_EXAMPLE_VAR variable:
32+
33+
.. code::
34+
35+
git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
36+
37+
For further information about how to set these variables, please refer to::
38+
39+
https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd
40+
41+
Here is a list of the most used variables:
42+
43+
QEMU_CI_AVOCADO_TESTING
44+
~~~~~~~~~~~~~~~~~~~~~~~
45+
By default, tests using the Avocado framework are not run automatically in
46+
the pipelines (because multiple artifacts have to be downloaded, and if
47+
these artifacts are not already cached, downloading them make the jobs
48+
reach the timeout limit). Set this variable to have the tests using the
49+
Avocado framework run automatically.
50+
1151
Jobs on Custom Runners
1252
======================
1353

0 commit comments

Comments
 (0)