From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] Add Dockerfile for CI
Date: Sun, 2 Jul 2017 23:46:04 +0200 [thread overview]
Message-ID: <20170702234604.77dc320e@windsurf> (raw)
In-Reply-To: <20170702161324.485-2-arnout@mind.be>
Hello,
On Sun, 2 Jul 2017 18:13:23 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> For Gitlab-CI, we want to avoid re-generating the minimal install to
> be able to run tests all the time. So let's create a docker image that
> we can post on Docker Hub and then pull.
>
> For the time being, this is just what we need for running our CI. Later
> we can produce something that is also useful for users.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> support/docker/Dockerfile | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 support/docker/Dockerfile
Applied to master, thanks. Will you provide an update to the Buildroot
manual, documenting this next to the Vagrant stuff?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-02 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 16:13 [Buildroot] [PATCH 1/3] .gitlab-ci.yml: run our runtime tests Arnout Vandecappelle
2017-07-02 16:13 ` [Buildroot] [PATCH 2/3] Add Dockerfile for CI Arnout Vandecappelle
2017-07-02 21:46 ` Thomas Petazzoni [this message]
2017-07-02 16:13 ` [Buildroot] [PATCH 3/3] .gitlab-ci.yml: use the Buildroot CI image published on Docker Hub Arnout Vandecappelle
2017-07-02 16:24 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2017-07-02 21:46 ` Thomas Petazzoni
2017-07-02 21:45 ` [Buildroot] [PATCH 1/3] .gitlab-ci.yml: run our runtime tests Thomas Petazzoni
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=20170702234604.77dc320e@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.