Home
last modified time | relevance | path

Searched +full:gitlab +full:- +full:ci (Results 1 – 25 of 56) sorted by relevance

123

/qemu/.gitlab-ci.d/
H A Dqemu-project.yml2 # https://gitlab.com/qemu-project/qemu/-/pipelines
9 - $RUNNER_TAG
12 - local: '/.gitlab-ci.d/base.yml'
13 - local: '/.gitlab-ci.d/stages.yml'
14 - local: '/.gitlab-ci.d/opensbi.yml'
15 - local: '/.gitlab-ci.d/containers.yml'
16 - local: '/.gitlab-ci.d/crossbuilds.yml'
17 - local: '/.gitlab-ci.d/buildtest.yml'
18 - local: '/.gitlab-ci.d/static_checks.yml'
19 - local: '/.gitlab-ci.d/custom-runners.yml'
[all …]
H A Dcirrus.yml1 # Jobs that we delegate to Cirrus CI because they require an operating
3 # setup has been performed on the GitLab account.
5 # The Cirrus CI configuration is generated by replacing target-specific
7 # when the GitLab CI job is defined, others are taken from a shell
11 # special care, because we can't just override it at the GitLab CI job
16 image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
21 # as there's often a 5-10 minute delay before Cirrus CI
25 - set -o allexport
26 - source .gitlab-ci.d/cirrus/$NAME.vars
27 - set +o allexport
[all …]
H A Dcustom-runners.yml1 # The CI jobs defined here require GitLab runners installed and
3 # versions and architectures. This is in contrast to the other CI
4 # jobs that are intended to run on GitLab's "shared" runners.
10 # gitlab-runner. To avoid problems that gitlab-runner can cause while
20 GIT_FETCH_EXTRA_FLAGS: --no-tags --prune --quiet
22 name: "$CI_JOB_NAME-$CI_COMMIT_REF_SLUG"
26 - build/build.ninja
27 - build/meson-logs
29 junit: build/meson-logs/testlog.junit.xml
32 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml'
[all …]
H A Dstatic_checks.yml1 check-patch:
4 image: python:3.10-alpine
7 - .gitlab-ci.d/check-patch.py
12 - apk -U add git perl
15 check-dco:
18 image: python:3.10-alpine
20 script: .gitlab-ci.d/check-dco.py
24 - apk -U add git
26 check-python-minreqs:
31 - make -C python check-minreqs
[all …]
H A Dopensbi.yml1 # All jobs needing docker-opensbi must use the same rules it uses.
5 - if: '$QEMU_CI != "1" && $QEMU_CI != "2" && $CI_PROJECT_NAMESPACE != "qemu-project"'
10 - if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project"'
12 - .gitlab-ci.d/opensbi.yml
13 - .gitlab-ci.d/opensbi/Dockerfile
14 - roms/opensbi/*
19 …- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project" && $CI_COMMIT_REF_NAME =~ /^open…
24 …- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project" && $CI_COMMIT_MESSAGE =~ /opensb…
28 - if: '$CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM && $CI_PIPELINE_SOURCE == "schedule"'
32 - changes:
[all …]
H A Dcrossbuild-template.yml7 - ccache
12 - source scripts/ci/gitlab-ci-section
13 - section_start setup "Pre-script setup"
14 - JOBS=$(expr $(nproc) + 1)
15 - cat /packages.txt
16 - section_end setup
18 - export CCACHE_BASEDIR="$(pwd)"
19 - export CCACHE_DIR="$CCACHE_BASEDIR/ccache"
20 - export CCACHE_MAXSIZE="500M"
21 - export PATH="$CCACHE_WRAPPERSDIR:$PATH"
[all …]
H A Dbuildtest-template.yml7 - ccache
11 - source scripts/ci/gitlab-ci-section
12 - section_start setup "Pre-script setup"
13 - JOBS=$(expr $(nproc) + 1)
14 - cat /packages.txt
15 - section_end setup
17 - export CCACHE_BASEDIR="$(pwd)"
18 - export CCACHE_DIR="$CCACHE_BASEDIR/ccache"
19 - export CCACHE_MAXSIZE="500M"
20 - export PATH="$CCACHE_WRAPPERSDIR:$PATH"
[all …]
H A Dcontainers.yml2 - local: '/.gitlab-ci.d/container-core.yml'
3 - local: '/.gitlab-ci.d/container-cross.yml'
5 amd64-alpine-container:
10 amd64-debian-container:
16 amd64-ubuntu2204-container:
21 amd64-opensuse-leap-container:
24 NAME: opensuse-leap
26 python-container:
31 amd64-fedora-rust-nightly-container:
34 NAME: fedora-rust-nightly
H A Dbuildtest.yml2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
H A Dcontainer-core.yml2 - local: '/.gitlab-ci.d/container-template.yml'
4 amd64-centos9-container:
9 amd64-fedora-container:
H A Dcheck-patch.py3 # check-patch.py: run checkpatch.pl across all commits in a branch
7 # SPDX-License-Identifier: GPL-2.0-or-later
14 namespace = "qemu-project"
20 repourl = "https://gitlab.com/%s/%s.git" % (namespace, reponame)
23 # GitLab CI environment does not give us any direct info about the
26 subprocess.check_call(["git", "remote", "add", "check-patch", repourl])
27 subprocess.check_call(["git", "fetch", "--refetch", "check-patch", "master"])
29 ancestor = subprocess.check_output(["git", "merge-base",
30 "check-patch/master", "HEAD"],
35 log = subprocess.check_output(["git", "log", "--format=%H %s",
[all …]
H A Dcrossbuilds.yml2 - local: '/.gitlab-ci.d/crossbuild-template.yml'
4 cross-armhf-user:
7 job: armhf-debian-cross-container
9 IMAGE: debian-armhf-cross
11 cross-arm64-system:
14 job: arm64-debian-cross-container
16 IMAGE: debian-arm64-cross
18 cross-arm64-user:
21 job: arm64-debian-cross-container
23 IMAGE: debian-arm64-cross
[all …]
/qemu/docs/devel/testing/
H A Dci-runners.rst.inc4 Besides the jobs run under the various CI systems listed before, there
6 These use the same GitLab CI's service/framework already used for all
7 other GitLab based CI jobs, but rely on additional systems, not the
8 ones provided by GitLab as "shared runners".
10 The architecture of GitLab's CI service allows different machines to
11 be set up with GitLab's "agent", called gitlab-runner, which will take
13 Here, the combination of a machine, properly configured with GitLab's
14 gitlab-runner, is called a "custom runner".
16 The GitLab CI jobs definition for the custom runners are located under::
18 .gitlab-ci.d/custom-runners.yml
[all …]
H A Dci-jobs.rst.inc3 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
9 ------------------------------------------------
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
18 ---------------------------------------------------------------------------
21 git-push command line arguments.
27 git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
31 https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd
[all …]
H A Dci.rst3 Continuous Integration (CI)
6 Continuous integration (CI) requires the builds of the entire application and
11 Most of QEMU's CI is run on GitLab's infrastructure although a number
12 of other CI services are used for specialised purposes. The most up to
14 `project wiki testing page <https://wiki.qemu.org/Testing/CI>`_.
25 .. include:: ci-jobs.rst.inc
26 .. include:: ci-runners.rst.inc
29 ----------
H A Dmain.rst7 everything from unit testing and exercising specific sub-systems all
9 tests you can run ``make check-help`` from either the source or build
16 [./pyvenv/bin/]meson test --suite qemu:softfloat
38 -------------------------
49 Different sub-types of "make check" tests will be explained below.
55 .. _unit-tests:
68 In QEMU, unit tests can be invoked with ``make check-unit``. They are
76 1. Create a new source file. For example, ``tests/unit/foo-test.c``.
86 is in ``tests/unit/foo-test.c``, it is enough to add an entry like::
90 'foo-test': [],
[all …]
/qemu/.gitlab-ci.d/cirrus/
H A DREADME.rst1 Cirrus CI integration
4 GitLab CI shared runners only provide a docker environment running on Linux.
5 While it is possible to provide private runners for non-Linux platforms this
8 To work around this limitation, we take advantage of `Cirrus CI`_'s free
9 offering: more specifically, we use the `cirrus-run`_ script to trigger Cirrus
10 CI jobs from GitLab CI jobs so that Cirrus CI job output is integrated into
11 the main GitLab CI pipeline dashboard.
13 There is, however, some one-time setup required. If you want FreeBSD and macOS
14 builds to happen when you push to your GitLab repository, you need to
17 This repository needs to exist for cirrus-run to work, but it doesn't need to
[all …]
H A Dmacos-14.vars1 # THIS FILE WAS AUTO-GENERATED
3 # $ lcitool variables macos-14 qemu
5 # https://gitlab.com/libvirt/libvirt-ci
14 …-sed gnutls gtk+3 gtk-vnc jemalloc jpeg-turbo json-c libcbor libepoxy libffi libgcrypt libiscsi li…
15 PYPI_PKGS='PyYAML numpy pillow sphinx sphinx-rtd-theme tomli'
H A Dfreebsd-14.vars1 # THIS FILE WAS AUTO-GENERATED
3 # $ lcitool variables freebsd-14 qemu
5 # https://gitlab.com/libvirt/libvirt-ci
14 …-lib bash bison bzip2 ca_root_nss capstone4 ccache4 cmocka ctags curl cyrus-sasl dbus diffutils dt…
/qemu/
H A D.gitlab-ci.yml2 # This is the GitLab CI configuration file for the mainstream QEMU
3 # project: https://gitlab.com/qemu-project/qemu/-/pipelines
10 # you need to set the location of your custom yml file at "custom CI/CD
11 # configuration path", on your GitLab CI namespace:
12 # https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path
14 # ----------------------------------------------------------------------
16 # QEMU CI jobs are based on templates. Some templates provide
17 # user-configurable options, modifiable via configuration variables.
19 # See https://qemu-project.gitlab.io/qemu/devel/ci.html#custom-ci-cd-variables
24 - local: '/.gitlab-ci.d/qemu-project.yml'
H A D.gitmodules3 url = https://gitlab.com/qemu-project/seabios.git/
6 url = https://gitlab.com/qemu-project/SLOF.git
9 url = https://gitlab.com/qemu-project/ipxe.git
12 url = https://gitlab.com/qemu-project/openbios.git
13 [submodule "roms/qemu-palcode"]
14 path = roms/qemu-palcode
15 url = https://gitlab.com/qemu-project/qemu-palcode.git
16 [submodule "roms/u-boot"]
17 path = roms/u-boot
18 url = https://gitlab.com/qemu-project/u-boot.git
[all …]
/qemu/docs/devel/
H A Dcodebase.rst12 ----------
15 `MAINTAINERS <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`_
20 - `Accelerators<Accelerators>`
21 - Block devices and `disk images<disk images>` support
22 - `CI<ci>` and `Tests<testing>`
23 - `Devices<device-emulation>` & Board models
24 - `Documentation <documentation-root>`
25 - `GDB support<GDB usage>`
26 - :ref:`Migration<migration>`
27 - `Monitor<QEMU monitor>`
[all …]
/qemu/scripts/ci/
H A Dgitlab-ci-section2 # SPDX-License-Identifier: GPL-2.0-or-later
4 # gitlab-ci-section: This is a shell script fragment which defines
6 # that GitLab will interpret as the beginning or end of a "collapsible
7 # section" in a CI job log. See
8 # https://docs.gitlab.com/ee/ci/yaml/script.html#expand-and-collapse-job-log-sections
11 # a CI config; the section_start and section_end functions will
14 # Section names are [-_.A-Za-z0-9] and the section_start pairs with
/qemu/tests/lcitool/
H A Drefresh3 # Re-generate container recipes
7 # https://gitlab.com/libvirt/libvirt-ci
13 # the top-level directory.
28 lcitool_path = Path(self_dir, "libvirt-ci", "bin", "lcitool")
30 lcitool_cmd = [lcitool_path, "--data-dir", self_dir]
63 " id ${USER} 2>/dev/null || useradd -u ${UID} -U ${USER}; fi\n"
70 cmd.extend(["--cross", cross])
82 filename = Path(src_dir, ".gitlab-ci.d", "cirrus", target + ".vars")
83 cmd = lcitool_cmd + ["variables", "--format", "shell", target, "qemu"]
89 cmd = lcitool_cmd + ["variables", "--format", "json", target, "qemu"]
[all …]
/qemu/tests/vm/generated/
H A DREADME1 # FILES IN THIS FOLDER WERE AUTO-GENERATED
3 # $ make lcitool-refresh
5 # https://gitlab.com/libvirt/libvirt-ci

123