Re: aarch64/arm builders

[Tristan Van Berkom <tristan vanberkom codethink co uk>]

On Thu, 2018-03-01 at 23:39 -0800, Christian Hergert wrote:
> On 03/01/2018 11:24 PM, Tristan Van Berkom wrote:
> > There is no automated publishing system either for the above mentioned
> > builders, instead from what I recall; Alex has to manually go and run a
> > script which pulls the latest builds from the machines and puts them on
> > sdk.gnome.org for consumption.
>
> Yeah, this is where we need the bits to be if we want people developing
> and testing their software against the SDK their software will
> ultimately be released with.
>
> For stable releases, I can get them via Flathub just fine it seems.
>
> -- Christian

Indeed, we have some prototyping for this, ultimately though it would
be nice to upstream the ostree-push work into ostree, which mostly
means rewriting it in C and working with Colin to make sure it's
implemented in a way that upstream can digest.

Dan Nicholson originally created some scripts for this, we've enhanced
and built upon this in BuildStream, and Sam Thursfield has extracted
our changes into a stand alone tool again:

   https://github.com/ssssam/ostree-push.git

The relevant upstream discussion starts in 2015:

   https://mail.gnome.org/archives/ostree-list/2015-October/msg00007.html

In the freedesktop-sdk project, Sam's fork is being used to publish
build results of what will be the 1.8 SDK:

   https://gitlab.com/freedesktop-sdk/freedesktop-sdk/blob/master/.gitlab-ci.yml#L224

For the GNOME SDK, doing it with BuildStream is the plan, based on the
same gnome-modulesets-base repo, the deployment of which we will surely
model after the work in the freedesktop-sdk project.

I'm not sure it makes sense to do this with the old flatpak-build-scripts
repo in interim, but I suppose if it's not too hard to setup, we could
do that too.

Another problem to consider is size of the growing repo; one of the
reasons Alex pulls stable releases manually afaik, is that if we were
to publish every single stable build, the repo would grow considerably
faster, and we may impose unnecessary upgrades on users.

Maybe for development branches we could publish every build, and just
wipe the repo once every release cycle (it's dev anyway).

Cheers,
    -Tristan