All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Fam Zheng" <famz@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] Add a gitlab-ci file for Continuous Integration testing on Gitlab
Date: Mon, 3 Sep 2018 16:15:53 +0100	[thread overview]
Message-ID: <20180903151553.GJ14377@redhat.com> (raw)
In-Reply-To: <1535987326-16222-1-git-send-email-thuth@redhat.com>

On Mon, Sep 03, 2018 at 05:08:46PM +0200, Thomas Huth wrote:
> This is very convenient for people who store their QEMU git trees on
> gitlab.com: Automatic CI pipelines are now run for each branch that is
> pushed to the server. Since the runtime of the jobs is limited to 1h
> we distribute the targets into multiple pipelines - this way the jobs
> finish within 30 minutes.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  In case somebody is interested, the result looks e.g. like this on gitlab:
>  https://gitlab.com/huth/qemu/pipelines/29255979
> 
>  .gitlab-ci.yml | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 48 insertions(+)
>  create mode 100644 .gitlab-ci.yml
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> new file mode 100644
> index 0000000..18a77bc
> --- /dev/null
> +++ b/.gitlab-ci.yml
> @@ -0,0 +1,48 @@
> +before_script:
> + - apt-get update -qq
> + - apt-get install -y -qq flex bison libglib2.0-dev libpixman-1-dev
> +
> +build-system1:
> + script:
> + - apt-get install -y -qq libgtk-3-dev libvte-dev nettle-dev libcacard-dev
> +      libusb-dev libvde-dev libspice-protocol-dev libgl1-mesa-dev
> + - ./configure --enable-werror --target-list="aarch64-softmmu alpha-softmmu
> +      cris-softmmu hppa-softmmu lm32-softmmu moxie-softmmu microblazeel-softmmu
> +      microblaze-softmmu mips-softmmu mips64el-softmmu m68k-softmmu ppc-softmmu"
> + - make -j2
> + - make -j2 check

Hmm, we already have a problem with the travis CI bulds that we're stuck
on outdated Ubuntu.

We also already have a set of dockerfiles in tests/docker/ for various
build configs maintaniers are expected to use.

Both Travis and GitLab CI are capable of using docker images.

What's blocking us in both Travis & GitLab cases is that we're not
publishing the docker images for QEMU yet. If we can get that working,
then all the CI can use pre-build docker images, saving the time
for downloading the same DPKG files each time, as the docker images
would be cached by the CI system IIUC.

The other reason I think it would be desirable is to get more consistency
between the various build systems used in QEMU.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      reply	other threads:[~2018-09-03 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 15:08 [Qemu-devel] [PATCH] Add a gitlab-ci file for Continuous Integration testing on Gitlab Thomas Huth
2018-09-03 15:15 ` Daniel P. Berrangé [this message]

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=20180903151553.GJ14377@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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.