Per project repository snapcraft files?

[Ben Cooksley]

On Sun, Aug 20, 2023 at 3:23 AM Nate Graham <nate at kde.org> wrote:

> So are these proposed CI jobs really intended to *release* the Snaps on
> the store? Is there any way to just build the Snaps locally?
>
> I ask because CI jobs run on every commit, so what we need them to test
> is that a proposed change hasn't broken Snap generation. We don't want
> to upload something to a remote server on every commit! It would be
> quite bad if KDE developers were unable to merge merge requests because
> an external server is down or overloaded.
>

I wasn't aware these jobs were going to be kicking off a publish to the
Snap Store - I thought this was just going to be producing an artifact ala.
Appimage / Flatpak / etc.
For those wondering, currently Snaps do tend to fail more often than
not when being built...

We cannot build them locally on our systems as the tooling for Snaps does
not support building within a Docker environment (as far as I have been
told, I can see a way you could probably do it but was told that is
definitely not going to work).

Last time I looked at the tooling for local builds, it was very messy and
had some rather interesting development decisions involved (including it's
own daemon for managing virtual machines, which had to be installed via
Snap naturally, and which segfaulted whenever it was asked to remove a VM).


> Nate
>

Regards,
Ben


>
>
> On 8/19/23 09:16, Scarlett Moore wrote:
> >
> >
> > On Sat, Aug 19, 2023, 7:48 AM Nate Graham <nate at kde.org
> > <mailto:nate at kde.org>> wrote:
> >
> >     Right now, our Flatpak CI jobs are self-contained; they generate a
> >     Flatpak without the need for any external servers. They're not
> >     uploading
> >     anything to FlatHub or elsewhere.
> >
> >     I might be misunderstanding something, but it seems like these
> proposed
> >     Snap CI jobs will be interacting with an external server in some way.
> >     Can you clarify that situation?
> >
> >     Nate
> >
> >
> > Yes, launchpad ( we already do this ) , however this time will be much
> > less as launchpad will build and upload the snaps to the store. Current
> > setup launchpad send back the snaps and we upload to the store.. also we
> > have issues getting logs for failures as these are temp jobs and
> > disappear quickly. Doing it the correct way with per repo snapcraft
> > files will solve many issues.
> > Thanks for your consideration,
> > Scarlett
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20230820/28cc6ce4/attachment.htm>