From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>,
Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] Public project sstate/hash equivalence mirror now live
Date: Sun, 12 Sep 2021 16:58:57 +0100 [thread overview]
Message-ID: <2f7b629ba49f76ad80461d00a3322a3fa1dc1b19.camel@linuxfoundation.org> (raw)
In-Reply-To: <95bf1261-eb40-cafa-3153-0c472142fb98@gmail.com>
On Sun, 2021-09-12 at 07:55 -0700, akuster808 wrote:
>
> On 9/12/21 4:46 AM, Richard Purdie wrote:
> > We made the autobuilder sstate public a while ago but it wasn't useful after we
> > switched to hash equivalence by default. I'm pleased to be able to report that
> > we now have a read-only public server for the hash equivalence. We did have to
> > fix a small API omission and a couple of sstate related bugs but I'm pleased to
> > be able to report it is now operational and usable. An example config would be:
> >
> > SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH"
> > BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687"
> >
> > I've included an example image build below where it took 11 minutes for a
> > core-image-minimal image build. Obviously this is only of benefit if you're
> > building configurations that match the project autobuilder although hash
> > equivalence could be useful alone in reducing some build times.
>
> What branches that support hash equivalence will be available other than
> Master?
The question doesn't make sense as hash equivalence doesn't have a "branch".
We're sharing any hash equivalence data generated from builds on the
autobuilder.
> > I have updated the local.conf sample file in poky to match the new release.
> > We're not widely highlighting that information as yet as it remains to be seen
> > how well it scales and what the hosting impacts for it will look like but it is
> > there to experiment with to a wider audience such as this list.
>
> The should improve the out-of-the-box experience.
Ultimately that is the hope.
Cheers,
Richard
next prev parent reply other threads:[~2021-09-12 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 11:46 Public project sstate/hash equivalence mirror now live Richard Purdie
2021-09-12 14:55 ` [OE-core] " Armin Kuster
2021-09-12 15:58 ` Richard Purdie [this message]
2021-09-12 16:01 ` Joshua Watt
2021-09-14 15:27 ` Konrad Weihmann
2021-09-14 16:26 ` Richard Purdie
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=2f7b629ba49f76ad80461d00a3322a3fa1dc1b19.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEWhacker@gmail.com \
--cc=akuster808@gmail.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox