<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 18, 2023, 12:53 PM Ben Cooksley <<a href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr">On Sat, Aug 19, 2023 at 7:45 AM Nicolas Fella <<a href="mailto:nicolas.fella@gmx.de" target="_blank" rel="noreferrer">nicolas.fella@gmx.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>Am 18.08.23 um 21:41 schrieb Ben
Cooksley:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">On Fri, Aug 18, 2023 at 10:17 PM Scarlett Moore
<<a href="mailto:scarlett.gately.moore@gmail.com" target="_blank" rel="noreferrer">scarlett.gately.moore@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Aug 18,
2023, 12:55 AM Ben Cooksley <<a href="mailto:bcooksley@kde.org" target="_blank" rel="noreferrer">bcooksley@kde.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr">On Fri, Aug 18, 2023 at 3:53 AM
Scarlett Moore <<a href="mailto:scarlett.gately.moore@gmail.com" rel="noreferrer noreferrer" target="_blank">scarlett.gately.moore@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello
everyone,<br>
</blockquote>
<div><br>
</div>
<div>Hey Scarlett,</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I am asking to revisit per project repo
snapcraft files. I see now<br>
that flatpak files are in project repos but I
understand this was<br>
rejected for snapcraft. I would like to
re-propose the idea, and here<br>
is why.<br>
The CI jobs for snap builds is cludgy at best.
We have huge amounts of<br>
failures because we must do a public upload to
launchpad which places<br>
us at the lowest priority and we have many
timeouts etc. Their<br>
solution is to create proper snap recipes
pointing to our repos with<br>
the snapcraft.yaml. Our current setup won't
work because we use<br>
subdirectories in one repo.<br>
Thoughts?<br>
</blockquote>
<div><br>
</div>
<div>My understanding (when automating the
triggering of these builds on <a href="http://invent.kde.org" rel="noreferrer noreferrer" target="_blank">invent.kde.org</a>
was discussed with Sysadmin) was that the Snap
folks had wanted to have everything in one
repository.</div>
<div>I had queried at the time why we weren't
adding a file into each repository (which is
what we do with Flatpak, and now with Craft as
well - although those builds have yet to be
widely rolled out)</div>
<div><br>
</div>
<div>With regards to the triggering of these
builds, how will this happen? </div>
<div>It sounds like what you are describing here
will result in Canonical servers polling <a href="http://invent.kde.org" rel="noreferrer noreferrer" target="_blank">invent.kde.org</a>
for changes, which is something we're not huge
fans of as most projects only change every
couple of days.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks for your time,<br>
Scarlett<br>
</blockquote>
<div><br>
</div>
<div>Cheers,</div>
<div>Ben </div>
</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Hi!</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks all for responding.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Albert: snapcraft files have been ironed
out. I have been quite busy over the last year doing so.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Ben: There is an option to have launchpad
build on changes which would have polling. However, I
would opt out of this feature and instead write some
tooling using launchpad API and Neons watcher tooling to
update versions and trigger launchpad builds. It would
actually lighten the load on KDE servers significantly. </div>
</div>
</blockquote>
<div><br>
</div>
<div>Yes, we would definitely want to opt out of that
completely - due to the number of repositories we have, any
kind of polling quickly turns into a fairly significant
number of requests.</div>
<div><br>
</div>
<div>Wouldn't you want to trigger this from a .gitlab-ci.yml
job definition though like we do for Flatpak and will be
doing very soon for all of the Craft builds that support
Android, Windows and Linux appimage binaries?</div></div></div></blockquote></div></blockquote></div></div></blockquote></div></div><div dir="auto">I am definitely game for following a standard and do what everyone else is doing. Just point me to instructions and I will do it.</div><div dir="auto">Thanks!</div><div dir="auto">Scarlett </div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><blockquote type="cite"><div dir="ltr"><div class="gmail_quote">
</div>
</div>
</blockquote>
I was about to ask how the "future binary-factory" on invent will
look like and suggest to follow that precedent. Can you elaborate on
that? Will these be jobs in the relevant repos or will there be a
meta-repo with all of the "release" jobs?<br></div></blockquote><div><br></div><div>The jobs will be sitting in the relevant repositories in a separate stage to the current CI.</div><div>There will not be a meta repo for this.</div><div><br></div><div>Individual applications for Craft will configure any extra behaviour they need via a .craft.ini file at top level in the repository, on the branch in question that the behaviour change is needed.</div><div>This is keeping in line with how our CI works (with .kde-ci.yml) and the Flatpak builds work (with .flatpak-manifest.json/yml).</div><div><br></div><div>Yet to be fully worked out how the triggering of them will be setup, whether it will be automatic or whether it will be manually run but that is an implementation detail.</div><div> </div><div>Cheers,</div><div>Ben</div></div></div>
</blockquote></div></div></div>