From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 3/3] .shippable.yml: new CI provider
Date: Tue, 14 Feb 2017 22:11:17 +0800 [thread overview]
Message-ID: <20170214141117.GC12294@lemon.lan> (raw)
In-Reply-To: <20170214100733.22280-4-alex.bennee@linaro.org>
On Tue, 02/14 10:07, Alex Bennée wrote:
> Ostensibly Shippable offers a similar set of services as Travis.
> However they are focused on Docker container based work-flows so we
> can use our existing containers to run a few extra builds - in this
> case a bunch of cross-compiled targets on a Debian multiarch system.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> ---
> v3
> - reduce matrix to armhf/arm64 which currently work
> - use the make docker-image-* build stanzas
> - add TARGET_LIST to each build
> ---
> .shippable.yml | 23 +++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 24 insertions(+)
> create mode 100644 .shippable.yml
>
> diff --git a/.shippable.yml b/.shippable.yml
> new file mode 100644
> index 0000000000..e4fa159481
> --- /dev/null
> +++ b/.shippable.yml
> @@ -0,0 +1,23 @@
> +language: c
> +env:
> + matrix:
> + - IMAGE=debian-armhf-cross
> + CROSS_PREFIX=arm-linux-gnueabihf-
> + TARGET_LIST=arm-softmmu,arm-linux-user
> + - IMAGE=debian-arm64-cross
> + CROSS_PREFIX=aarch64-linux-gnu-
> + TARGET_LIST=aarch64-softmmu,aarch64-linux-user
> + - IMAGE=centos6
> + TARGET_LIST=i386-softmmu,x86_64-softmmu
> +build:
> + pre_ci:
> + - make docker-image-${IMAGE}
> + pre_ci_boot:
> + image_name: qemu
> + image_tag: ${IMAGE}
> + pull: false
> + options: "-e HOME=/root"
> + ci:
> + - unset CC
> + - ./configure --cross-prefix=${CROSS_PREFIX} --target-list=${TARGET_LIST}
> + - make -j2
Looks cool!
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7afbadaa15..578888d32d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1805,6 +1805,7 @@ M: Alex Bennée <alex.bennee@linaro.org>
> L: qemu-devel@nongnu.org
> S: Supported
> F: .travis.yml
> +F: .shippable.yml
>
> Documentation
> -------------
> --
> 2.11.0
>
>
May I propose we merge 'docker testing' section of MAINTAINERS into 'build and
test automation' section? I don't know as much about travis (and shippable) but
I'm totally fine if you want to have docker tests under your umbrella, and
it seems a logical step judging from their names.
Fam
next prev parent reply other threads:[~2017-02-14 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:07 [Qemu-devel] [PATCH v3 0/3] Docker cross-compile targets and user build support Alex Bennée
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 1/3] tests/docker: add basic user mapping support Alex Bennée
2017-02-14 14:22 ` Fam Zheng
2017-02-14 15:11 ` Alex Bennée
2017-02-14 15:20 ` Fam Zheng
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 2/3] new: debian docker targets for cross-compiling Alex Bennée
2017-02-14 14:00 ` Fam Zheng
2017-02-14 14:27 ` Fam Zheng
2017-02-14 15:10 ` Alex Bennée
2017-02-14 14:30 ` Peter Maydell
2017-02-14 15:09 ` Alex Bennée
2017-02-14 15:18 ` Fam Zheng
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 3/3] .shippable.yml: new CI provider Alex Bennée
2017-02-14 14:11 ` Fam Zheng [this message]
2017-02-14 15:56 ` Alex Bennée
2017-02-15 0:51 ` Fam Zheng
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=20170214141117.GC12294@lemon.lan \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--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).