qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"open list:-----------------..." <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH v2 6/7] .shippable.yml: new CI provider
Date: Tue, 24 Jan 2017 14:33:45 +0000	[thread overview]
Message-ID: <20170124143346.22240-7-alex.bennee@linaro.org> (raw)
In-Reply-To: <20170124143346.22240-1-alex.bennee@linaro.org>

Ostensibly Shippable offers a similar set of services as Travis.
However they are focused on 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>
---
 .shippable.yml | 24 ++++++++++++++++++++++++
 MAINTAINERS    |  1 +
 2 files changed, 25 insertions(+)
 create mode 100644 .shippable.yml

diff --git a/.shippable.yml b/.shippable.yml
new file mode 100644
index 0000000000..10496acb7c
--- /dev/null
+++ b/.shippable.yml
@@ -0,0 +1,24 @@
+language: c
+env:
+  matrix:
+    - CROSS_ARCH=armhf   CROSS_PREFIX=arm-linux-gnueabihf-
+    - CROSS_ARCH=arm64   CROSS_PREFIX=aarch64-linux-gnu-
+    - CROSS_ARCH=mipsel  CROSS_PREFIX=mipsel-linux-gnu-
+    - CROSS_ARCH=ppc64el CROSS_PREFIX=powerpc64le-linux-gnu-
+build:
+  pre_ci:
+    - mkdir -p docker-build
+    - cp ./tests/docker/dockerfiles/debian-multiarch-cross.docker docker-build/Dockerfile
+    - docker build -t debian-multiarch-cross:base docker-build
+    - echo -e "FROM debian-multiarch-cross:base\nRUN apt-get build-dep -a ${CROSS_ARCH} -qq qemu" | docker build -t debian-multiarch-cross:${CROSS_ARCH} -
+  pre_ci_boot:
+    image_name: debian-multiarch-cross
+    image_tag: ${CROSS_ARCH}
+    pull: false
+    options: "-e HOME=/root"
+  ci:
+    - env
+    - apt-get build-dep -a ${CROSS_ARCH} -qq qemu
+    - unset CC
+    - ./configure --cross-prefix=${CROSS_PREFIX}
+    - make -j2
diff --git a/MAINTAINERS b/MAINTAINERS
index ad1000415d..5e7d1a7548 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1784,6 +1784,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

  parent reply	other threads:[~2017-01-24 14:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170124143346.22240-1-alex.bennee@linaro.org>
2017-01-24 14:33 ` [Qemu-devel] [PATCH v2 1/7] .travis.yml: don't specify CONFIG twice Alex Bennée
2017-01-24 14:33 ` [Qemu-devel] [PATCH v2 2/7] .travis.yml: split VM based builds Alex Bennée
2017-01-24 14:33 ` [Qemu-devel] [PATCH v2 3/7] .travis.yml: DEBUG MacOSX build Alex Bennée
2017-01-26 11:26   ` Fam Zheng
2017-01-26 12:46     ` Alex Bennée
2017-01-24 14:33 ` [Qemu-devel] [PATCH v2 4/7] tests/docker: add basic user mapping support Alex Bennée
2017-01-26  9:08   ` Fam Zheng
2017-01-24 14:33 ` [Qemu-devel] [PATCH v2 5/7] new debian-multiarch-cross.docker: a cross-compiling docker guest Alex Bennée
2017-01-26 10:53   ` Fam Zheng
2017-01-26 12:48     ` Alex Bennée
2017-01-24 14:33 ` Alex Bennée [this message]
2017-01-24 14:33 ` [Qemu-devel] [PATCH v2 7/7] qemu-options: remove stray space Alex Bennée
2017-01-26 11:15   ` 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=20170124143346.22240-7-alex.bennee@linaro.org \
    --to=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).