From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, famz@redhat.com
Subject: [Qemu-devel] [PATCH v7 00/10] docker: Support building qemu-user powered docker test images
Date: Tue, 19 Jul 2016 21:20:35 +0800 [thread overview]
Message-ID: <1468934445-32183-1-git-send-email-famz@redhat.com> (raw)
v7: Pick up Alex's branch, and add the "docker.py images" patch. Changes since
v6:
- Added the EXECUTABLE patch.
- Fix rc == 0 case of pre script.
- Add docker.py images subcommand.
- Use docker.py instead of sudo.
- More details in message of the debian bootstrap pre script.
v6: A few tweaks to make this more mergable. Including:
- Add and catch magic pre script exit code "3" to allow skipping image.
- Tweak debian-bootstrap.pre to return '3' when appropriate (It should
still return 1 for debootstrap command failure).
- Fix "realpath" to "readlink -e" to be compatible with centos6.
- Add the last patch to skip test if the image is skipped by .pre.
Alex, if this looks good to you, I can send a pull req today.
Alex Bennée (6):
tests/docker/docker.py: docker_dir outside build
tests/docker/docker.py: support --include-executable
tests/docker/docker.py: check and run .pre script
tests/docker/dockerfiles: new debian-bootstrap.docker
tests/docker/docker.py: add update operation
docker: pass EXECUTABLE to build script
Fam Zheng (4):
docker: More sensible run script
docker: Fix exit code if $CMD failed
docker: Add "images" subcommand to docker.py
docker: Don't start a container that doesn't exist
tests/docker/Makefile.include | 14 +-
tests/docker/docker.py | 159 +++++++++++++++++++++--
tests/docker/dockerfiles/debian-bootstrap.docker | 21 +++
tests/docker/dockerfiles/debian-bootstrap.pre | 87 +++++++++++++
tests/docker/run | 16 ++-
5 files changed, 280 insertions(+), 17 deletions(-)
create mode 100644 tests/docker/dockerfiles/debian-bootstrap.docker
create mode 100755 tests/docker/dockerfiles/debian-bootstrap.pre
--
2.7.4
next reply other threads:[~2016-07-19 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 13:20 Fam Zheng [this message]
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 01/10] tests/docker/docker.py: docker_dir outside build Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 02/10] tests/docker/docker.py: support --include-executable Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 03/10] tests/docker/docker.py: check and run .pre script Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 04/10] tests/docker/dockerfiles: new debian-bootstrap.docker Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 05/10] tests/docker/docker.py: add update operation Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 06/10] docker: More sensible run script Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 07/10] docker: Fix exit code if $CMD failed Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 08/10] docker: Add "images" subcommand to docker.py Fam Zheng
2016-07-19 14:00 ` Alex Bennée
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 09/10] docker: Don't start a container that doesn't exist Fam Zheng
2016-07-19 13:20 ` [Qemu-devel] [PATCH v7 10/10] docker: pass EXECUTABLE to build script 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=1468934445-32183-1-git-send-email-famz@redhat.com \
--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).