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.
Nate
On 8/19/23 09:16, Scarlett Moore wrote:
On Sat, Aug 19, 2023, 7:48 AM Nate Graham <n...@kde.org
<mailto:n...@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
