From: Stefano Stabellini <sstabellini@kernel.org>
To: Anthony PERARD <anthony.perard@citrix.com>, cardoe@cardoe.com
Cc: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org, iwj@xenproject.org, wl@xen.org,
andrew.cooper3@citrix.com,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Solving the gitlab-ci git fetch issue, was: [PATCH 3/3] automation: add a QEMU based x86_64 Dom0/DomU test
Date: Wed, 27 Oct 2021 14:43:46 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2110271437120.20134@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <YXlbOjiphjN/XqMz@perard>
On Wed, 27 Oct 2021, Anthony PERARD wrote:
> > But we do have a severe problem at the moment with external sources: our
> > "git clones" keep failing during the build on x86. That is definitely
> > something worth improving (see my other email thread on the subject) and
> > it is the main problem affecting gitlab-ci at the moment, I keep having
> > to restart jobs almost daily to get the overall pipeline to "pass".
> >
> > If you have any ideas on how to stop fetching things using "git" from
> > external repositories in gitlab-ci that would be fantastic :-)
> > The only thing I could think of to "fix it" is moving all external repos
> > to gitlab repositories mirrors.
>
> I don't think that would work, I've seen the initial clone/fetch of a
> job fail as well, so from gitlab. If we could have a cache of those
> external resources closer to the runners, that would be better.
You mean like a git repository mirror inside the Rackspace network (the
provider of the x86 runner), right? Then we would force the git client
to go to the Rackspace mirror instead of directly to the target using
"insteadOf".
Is that what you meant? Doug, do you think it would work?
next prev parent reply other threads:[~2021-10-27 21:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 23:08 [PATCH 0/3] automation: introduce an x86_64 Dom0/DomU test Stefano Stabellini
2021-10-21 23:08 ` [PATCH 1/3] automation: add x86_64 alpine 3.12 test-artifact Stefano Stabellini
2021-10-22 12:37 ` Anthony PERARD
2021-10-22 12:54 ` Andrew Cooper
2021-10-22 20:01 ` Stefano Stabellini
2021-10-21 23:08 ` [PATCH 2/3] automation: Linux 5.10.74 test-artifact Stefano Stabellini
2021-10-22 12:38 ` Anthony PERARD
2021-10-22 20:02 ` Stefano Stabellini
2021-10-22 13:00 ` Andrew Cooper
2021-10-22 19:41 ` Stefano Stabellini
2021-10-25 5:15 ` Juergen Gross
2021-10-26 0:54 ` Stefano Stabellini
2021-10-27 7:34 ` Juergen Gross
2021-10-27 22:44 ` Stefano Stabellini
2021-10-27 23:24 ` Stefano Stabellini
2021-10-28 7:00 ` Juergen Gross
2021-10-28 16:41 ` Stefano Stabellini
2021-10-29 5:43 ` Juergen Gross
2021-11-02 0:12 ` Stefano Stabellini
2021-10-21 23:08 ` [PATCH 3/3] automation: add a QEMU based x86_64 Dom0/DomU test Stefano Stabellini
2021-10-22 13:03 ` Anthony PERARD
2021-10-22 20:05 ` Stefano Stabellini
2021-10-25 16:13 ` Anthony PERARD
2021-10-26 1:33 ` Stefano Stabellini
2021-10-27 13:59 ` Anthony PERARD
2021-10-27 21:43 ` Stefano Stabellini [this message]
2021-10-28 9:48 ` Solving the gitlab-ci git fetch issue, was: " Anthony PERARD
2021-10-28 14:19 ` Stefano Stabellini
2021-10-22 9:25 ` [PATCH 0/3] automation: introduce an " Ian Jackson
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=alpine.DEB.2.21.2110271437120.20134@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=iwj@xenproject.org \
--cc=stefano.stabellini@xilinx.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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.