From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>, "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] [PATCH v2] Add a gitlab-ci file for Continuous Integration testing on Gitlab
Date: Wed, 13 Feb 2019 14:03:40 +0000 [thread overview]
Message-ID: <87imxniy4j.fsf@zen.linaroharston> (raw)
In-Reply-To: <9336d69b-8896-4a19-c580-b6ce5aefec2d@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> On 2019-02-13 13:06, Marc-André Lureau wrote:
>> Hi
>>
>> On Wed, Feb 13, 2019 at 12:55 PM Thomas Huth <thuth@redhat.com> wrote:
>>>
>>> This is very convenient for people like me who store their QEMU git trees
>>> on gitlab.com: Automatic CI pipelines are now run for each branch that is
>>> pushed to the server - useful for some extra-testing before sending PULL-
>>> requests for example. Since the runtime of the jobs is limited to 1h, the
>>> jobs are distributed into multiple pipelines - this way everything finishs
>>> fine within time (ca. 30 minutes currently).
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>> An example can be seen here: https://gitlab.com/huth/qemu/pipelines/
>>>
>>> I'd really like to get this into the main QEMU repository, so that I don't
>>> have to cherry-pick this patch onto my testing branches anymore each time
>>> I want to test before sending a PULL request...
>>>
>>> .gitlab-ci.yml | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> MAINTAINERS | 5 ++++
>>> 2 files changed, 78 insertions(+)
>>> create mode 100644 .gitlab-ci.yml
>>>
>>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>> new file mode 100644
>>> index 0000000..79d02cf
>>> --- /dev/null
>>> +++ b/.gitlab-ci.yml
>>> @@ -0,0 +1,73 @@
>>> +before_script:
>>> + - apt-get update -qq
>>> + - apt-get install -y -qq flex bison libglib2.0-dev libpixman-1-dev genisoimage
>>> +
>>> +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
>>> + mips64el-softmmu m68k-softmmu ppc-softmmu riscv64-softmmu sparc-softmmu"
>>> + - make -j2
>>
>> Have you tried $(nproc) ?
>
> The containers are only single CPU there. I'm using -j2 just in case one
> of the processes is blocked by waiting for IO, the other one can still
> continue compiling.
>
>> Despite the duplication of CI files, which is not really a problem imho,
>>
>> lgtm,
>> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Thanks!
>
> And yes, I also think the duplication of the CI files should not really
> be a problem - it's rather a plus since we also got test variations this
> way. I already found some bugs with this here that were not detected by
> the other CI setups yet (e.g. since one of the pipelines uses
> --disable-replication and other --disable-xxx flags).
Sure I'm happy to have a thousand flowers bloom in this regard.
Do you know if gitlab does build status buttons like the others?
--
Alex Bennée
next prev parent reply other threads:[~2019-02-13 14:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 11:54 [Qemu-devel] [PATCH v2] Add a gitlab-ci file for Continuous Integration testing on Gitlab Thomas Huth
2019-02-13 12:06 ` Marc-André Lureau
2019-02-13 12:20 ` Thomas Huth
2019-02-13 14:03 ` Alex Bennée [this message]
2019-02-13 14:06 ` Marc-André Lureau
2019-02-18 18:22 ` Cleber Rosa
2019-02-19 6:44 ` Thomas Huth
2019-02-19 7:53 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-02-19 9:04 ` [Qemu-devel] Failing iotests in CI (was: Add a gitlab-ci file for Continuous Integration testing on Gitlab) Thomas Huth
2019-02-19 9:37 ` Kevin Wolf
2019-02-19 10:11 ` Thomas Huth
2019-02-19 11:38 ` Kevin Wolf
2019-02-19 12:09 ` Thomas Huth
2019-02-19 11:06 ` Daniel P. Berrangé
2019-02-19 11:31 ` Kevin Wolf
2019-02-19 12:01 ` Daniel P. Berrangé
2019-02-19 12:04 ` Daniel P. Berrangé
2019-02-19 12:16 ` Kevin Wolf
2019-02-19 12:51 ` Daniel P. Berrangé
2019-02-20 11:27 ` [Qemu-devel] [PATCH v2] Add a gitlab-ci file for Continuous Integration testing on Gitlab Paolo Bonzini
2019-02-20 11:35 ` Alex Bennée
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=87imxniy4j.fsf@zen.linaroharston \
--to=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=marcandre.lureau@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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 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).