From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 2/3] gitlab: add fine grained job deps for all build jobs
Date: Tue, 9 Feb 2021 07:39:17 +0100 [thread overview]
Message-ID: <83604b7c-eceb-b34c-1a7d-3f491b36b704@redhat.com> (raw)
In-Reply-To: <20210208163339.1159514-3-berrange@redhat.com>
On 08/02/2021 17.33, Daniel P. Berrangé wrote:
> This allows the build jobs to start running as soon as their respective
> container image is ready, instead of waiting for all container builds
> to finish.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.yml | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
Please also adjust .gitlab-ci.d/crossbuilds.yml
Thanks,
Thomas
next prev parent reply other threads:[~2021-02-09 6:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 16:33 [PATCH 0/3] fix build failures from incorrectly skipped container build jobs Daniel P. Berrangé
2021-02-08 16:33 ` [PATCH 1/3] gitlab: always build container images Daniel P. Berrangé
2021-02-09 6:37 ` Thomas Huth
2021-02-09 9:58 ` Daniel P. Berrangé
2021-02-10 11:17 ` Daniel P. Berrangé
2021-02-16 12:43 ` Daniel P. Berrangé
2021-02-16 13:02 ` Philippe Mathieu-Daudé
2021-02-16 13:15 ` Daniel P. Berrangé
2021-02-08 16:33 ` [PATCH 2/3] gitlab: add fine grained job deps for all build jobs Daniel P. Berrangé
2021-02-09 6:39 ` Thomas Huth [this message]
2021-02-08 16:33 ` [PATCH 3/3] gitlab: fix inconsistent indentation Daniel P. Berrangé
2021-02-08 17:20 ` Philippe Mathieu-Daudé
2021-02-08 17:22 ` [PATCH 0/3] fix build failures from incorrectly skipped container build jobs Daniel P. Berrangé
2021-02-08 18:08 ` Philippe Mathieu-Daudé
2021-02-08 18:12 ` Daniel P. Berrangé
2021-02-09 6:01 ` Stefan Weil
2021-02-09 6:55 ` Thomas Huth
2021-02-09 9:53 ` Daniel P. Berrangé
2021-02-16 10:39 ` Philippe Mathieu-Daudé
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=83604b7c-eceb-b34c-1a7d-3f491b36b704@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).