[OE-core] Connectivity check uris

Andre McCurdy armccurdy at gmail.com
Thu Jan 23 19:25:58 UTC 2020


On Thu, Jan 23, 2020 at 7:24 AM Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> On Thu, 2020-01-23 at 09:59 -0500, Jean-Marie LEMETAYER wrote:
> > On Jan 23, 2020, at 3:37 PM, Richard Purdie
> > richard.purdie at linuxfoundation.org wrote:
> > > On Thu, 2020-01-23 at 09:22 -0500, Jean-Marie LEMETAYER wrote:
> > > > I understand the issue with blocked domains this is why I suggest
> > > > the
> > > > custom domain "connectivitycheck.openembedded.org".
> > > >
> > > > But I dont know if it could be an option. Can OE have a sub-
> > > > domain
> > > > like that? maybe using some cdn to handle the load?
> > >
> > > We can certainly setup domains but we can't easily get a cdn. I'd
> > > be
> > > worried about OE's response time too.
> > >
> > > > Another option will be to provide multiple URIs:
> > > >     CONNECTIVITY_CHECK_URIS ?= " \
> > > >         https://google.com \
> > > >         https://www.bing.com \
> > > >         https://www.baidu.com \
> > > >     "
> > >
> > > Looking at the code, I wonder if a CONNECTIVITY_CHECK_MIRRORS,
> > > injected
> > > into MIRRORS internally with google as the default and baidu as the
> > > mirror would work?

How about checking github.com? That's probably the host that a network
dependent build needs to access most often.


More information about the Openembedded-core mailing list