From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [RFC PATCH] ci: ensure that all jobs use a shallow clone
Date: Thu, 7 Jan 2021 20:05:22 +0100 [thread overview]
Message-ID: <dff4499e-eb4d-f96b-5f82-51352561d231@redhat.com> (raw)
In-Reply-To: <20210107182812.GI1029501@redhat.com>
On 07/01/2021 19.28, Daniel P. Berrangé wrote:
[...]
> Travis has issues with git cloning and concurrent pushes.
>
> eg if you push branch A, it schedules a CI job. Then you
> push branch B before jobs for A have started.
>
> When the job for A starts, it will be unable to checkout
> the commit for branch A's merge because the history will
> be too shallow.
I think we have to get rid of travis.yml soon anyway, since they changed
their business model, and soon it won't be possible anymore to use it for
QEMU. travis-ci.org is getting decommissioned and on travis-ci.com you can
only get free CI minutes for non-sponsored FOSS projects.
So let's simply not worry about Travis-CI anymore.
>> .cirrus.yml | 1 +
>> .gitlab-ci.yml | 3 +++
>> .shippable.yml | 2 ++
Maybe we could rather disable shippable now that we support the cross
container builds on gitlab-ci, too?
Thomas
next prev parent reply other threads:[~2021-01-07 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 17:17 [RFC PATCH] ci: ensure that all jobs use a shallow clone Paolo Bonzini
2021-01-07 18:28 ` Daniel P. Berrangé
2021-01-07 19:05 ` Thomas Huth [this message]
2021-01-07 19:23 ` Paolo Bonzini
2021-01-08 10:16 ` Daniel P. Berrangé
2021-01-08 11:06 ` Thomas Huth
2021-01-08 11:10 ` Daniel P. Berrangé
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=dff4499e-eb4d-f96b-5f82-51352561d231@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.