From: "Alex Bennée" <alex.bennee@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 3/4] .shippable.yml: new CI provider
Date: Thu, 16 Feb 2017 19:40:32 +0000 [thread overview]
Message-ID: <871suxc4b3.fsf@linaro.org> (raw)
In-Reply-To: <20170216133109.GD8817@lemon.lan>
Fam Zheng <famz@redhat.com> writes:
> On Thu, 02/16 12:34, 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.
>
> Out of curiosity, what are the forms of build report from shippable
> service?
It sends out emails and there is the web status page:
https://app.shippable.com/runs/58a596c4266ed80f003a9385/summary
There is also support for build badges a.la Travis.
>
>>
>> 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 | 21 +++++++++++++++++++++
>> 1 file changed, 21 insertions(+)
>> create mode 100644 .shippable.yml
>>
>> diff --git a/.shippable.yml b/.shippable.yml
>> new file mode 100644
>> index 0000000000..4de8daf341
>> --- /dev/null
>> +++ b/.shippable.yml
>> @@ -0,0 +1,21 @@
>> +language: c
>> +env:
>> + matrix:
>> + - IMAGE=debian-armhf-cross
>> + TARGET_LIST=arm-softmmu,arm-linux-user
>> + - IMAGE=debian-arm64-cross
>> + 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 ${QEMU_CONFIGURE_OPTS} --target-list=${TARGET_LIST}
>> + - make -j2
>
> It's a good surprise that our docker infrastructure fits in the shippable
> framework pretty nicely. :)
>
> Looks good to me without cross checking the shippable API:
>
> Reviewed-by: Fam Zheng <famz@redhat.com>
--
Alex Bennée
next prev parent reply other threads:[~2017-02-16 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 12:34 [Qemu-devel] [PATCH v4 0/4] Docker cross-compile targets and user build support Alex Bennée
2017-02-16 12:34 ` [Qemu-devel] [PATCH v4 1/4] tests/docker: add basic user mapping support Alex Bennée
2017-02-16 13:15 ` Fam Zheng
2017-02-19 5:24 ` Philippe Mathieu-Daudé
2017-02-20 9:01 ` Alex Bennée
2017-02-16 12:34 ` [Qemu-devel] [PATCH v4 2/4] new: debian docker targets for cross-compiling Alex Bennée
2017-02-16 13:19 ` Fam Zheng
2017-02-19 4:34 ` Philippe Mathieu-Daudé
2017-02-20 9:02 ` Alex Bennée
2017-02-16 12:34 ` [Qemu-devel] [PATCH v4 3/4] .shippable.yml: new CI provider Alex Bennée
2017-02-16 13:31 ` Fam Zheng
2017-02-16 19:40 ` Alex Bennée [this message]
2017-02-16 12:34 ` [Qemu-devel] [PATCH v4 4/4] MAINTAINERS: merge Build and test automation with Docker tests Alex Bennée
2017-02-16 13:23 ` Fam Zheng
2017-02-16 13:36 ` [Qemu-devel] [PATCH v4 0/4] Docker cross-compile targets and user build support 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=871suxc4b3.fsf@linaro.org \
--to=alex.bennee@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.