From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Fam Zheng" <famz@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [Qemu-devel] [PATCH] Add a gitlab-ci file for Continuous Integration testing on Gitlab
Date: Mon, 3 Sep 2018 17:08:46 +0200 [thread overview]
Message-ID: <1535987326-16222-1-git-send-email-thuth@redhat.com> (raw)
This is very convenient for people who store their QEMU git trees on
gitlab.com: Automatic CI pipelines are now run for each branch that is
pushed to the server. Since the runtime of the jobs is limited to 1h
we distribute the targets into multiple pipelines - this way the jobs
finish within 30 minutes.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
In case somebody is interested, the result looks e.g. like this on gitlab:
https://gitlab.com/huth/qemu/pipelines/29255979
.gitlab-ci.yml | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 .gitlab-ci.yml
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
new file mode 100644
index 0000000..18a77bc
--- /dev/null
+++ b/.gitlab-ci.yml
@@ -0,0 +1,48 @@
+before_script:
+ - apt-get update -qq
+ - apt-get install -y -qq flex bison libglib2.0-dev libpixman-1-dev
+
+build-system1:
+ script:
+ - apt-get install -y -qq libgtk-3-dev libvte-dev nettle-dev libcacard-dev
+ libusb-dev libvde-dev libspice-protocol-dev libgl1-mesa-dev
+ - ./configure --enable-werror --target-list="aarch64-softmmu alpha-softmmu
+ cris-softmmu hppa-softmmu lm32-softmmu moxie-softmmu microblazeel-softmmu
+ microblaze-softmmu mips-softmmu mips64el-softmmu m68k-softmmu ppc-softmmu"
+ - make -j2
+ - make -j2 check
+
+build-system2:
+ script:
+ - apt-get install -y -qq libsdl2-dev libgcrypt-dev libbrlapi-dev libaio-dev
+ libfdt-dev liblzo2-dev librdmacm-dev libibverbs-dev libibumad-dev
+ - ./configure --enable-werror --target-list="tricore-softmmu unicore32-softmmu
+ riscv32-softmmu riscv64-softmmu s390x-softmmu sh4-softmmu sparc-softmmu
+ sparc64-softmmu x86_64-softmmu xtensa-softmmu nios2-softmmu or1k-softmmu"
+ - make -j2
+ - make -j2 check
+
+build-clang:
+ script:
+ - apt-get install -y -qq clang libgtk-3-dev libsdl2-dev libbluetooth-dev
+ xfslibs-dev libiscsi-dev libnfs-dev libseccomp-dev gnutls-dev librbd-dev
+ - CC="clang" ./configure --enable-werror --target-list="tilegx-linux-user
+ arm-softmmu i386-softmmu ppc64-softmmu s390x-softmmu sparc-softmmu"
+ - make -j2
+ - make -j2 check
+
+build-disabled:
+ script:
+ - ./configure --enable-werror --disable-tcg --disable-slirp --disable-libxml2
+ --disable-capstone --disable-live-block-migration --disable-glusterfs
+ --disable-replication --disable-coroutine-pool --disable-smartcard
+ --disable-guest-agent --disable-curses --disable-curl --disable-tpm
+ --disable-qom-cast-debug --disable-spice --disable-vhost-vsock
+ --disable-vhost-net --disable-vhost-crypto --disable-vhost-user
+ - make -j2
+
+build-user:
+ script:
+ - ./configure --enable-werror --disable-system --disable-guest-agent
+ - make -j2
+ - make -j2 check
--
1.8.3.1
next reply other threads:[~2018-09-03 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 15:08 Thomas Huth [this message]
2018-09-03 15:15 ` [Qemu-devel] [PATCH] Add a gitlab-ci file for Continuous Integration testing on Gitlab Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1535987326-16222-1-git-send-email-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).