Lines Matching full:ci
3 Custom CI/CD variables
6 QEMU CI pipelines can be tuned by setting some CI environment variables.
8 Set variable globally in the user's CI namespace
11 Variables can be set globally in the user's CI namespace setting.
15 https://docs.gitlab.com/ee/ci/variables/#add-a-cicd-variable-to-a-project
27 git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
37 CI configurations. For example define an alias for triggering CI:
41 git config --local alias.push-ci "push -o ci.variable=QEMU_CI=1"
42 git config --local alias.push-ci-now "push -o ci.variable=QEMU_CI=2"
48 git push-ci
54 git push-ci-now
62 The variables used by QEMU's CI configuration are grouped together
70 repository CI settings, or as git push variables, to influence
92 CI configuration file.
97 The job makes use of Cirrus CI infrastructure, requiring the
104 by default due to need to conserve limited CI resources. It is
105 available to be started manually by the contributor in the CI
113 CI pipeline.
144 in order to preserve CI credits
167 If you've got access to an aarch64 host that can be used as a gitlab-CI
174 aarch32 EL0 code to be used as a gitlab-CI runner, you can set this
180 If you've got access to an IBM Z host that can be used as a gitlab-CI