ci: re-enable arm64 snap builds via remote-build#1273
Conversation
Use snapcraft's remote-build feature to outsource building on arm64 to Launchpad's build servers. This needs a new secret: LAUNCHPAD_CREDENTIALS It can be sourced from a local snapcraft installation that has performed a remote build, or a Launchpad login, before: ~/.local/share/snapcraft/launchpad/credentials Also fix a problem related to file permissions in override-pull and declare all snaps stable, regardless of whether they are built from tagged commits.
|
@phkahler This strategy appears to be working well for the official KDE snaps: https://invent.kde.org/packaging/snapcraft-kde-applications/-/jobs/423670 So, (a) Do you want this at all? and (b) Do you want me to register a solvespace Launchpad account for this? Best would be to register with an email that you control. We could do your gmail with a '+launchpad-solvespace' suffix (https://support.google.com/a/users/answer/9308648?hl=en). |
|
This is the old SolveSpace launchpad account, registered by whitequark: https://launchpad.net/~solvespace |
|
@ppd @phkahler @vespakoen Since this is the currently open CI issue I'll write here to avoid extra "noise". Sorry for the unrelated topic and spamming you all. The macOS CI build is failing (again) https://github.com/solvespace/solvespace/runs/7938462623?check_suite_focus=true :
|
ruevs
force-pushed
the
master
branch
2 times, most recently
from
93215ea to
bc2bca8
Compare
3 participants
Use snapcraft's remote-build feature to outsource building
on arm64 to Launchpad's build servers.
This needs a new secret: LAUNCHPAD_CREDENTIALS
It can be sourced from a local snapcraft installation that has
performed a remote build, or a Launchpad login, before:
~/.local/share/snapcraft/launchpad/credentials
Also fix a problem related to file permissions in override-pull
and declare all snaps stable, regardless of whether they are built
from tagged commits.