git-ubuntu unavailable on non-amd64 architectures

Bug #1915507 reported by Nafallo Bjälevik
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
git-ubuntu
Triaged
Wishlist
Unassigned

Bug Description

it seems the git-ubuntu snap is missing on arm64. Could that be built and published please? :-)

Tags: snap
Revision history for this message
Robie Basak (racb) wrote :

This would need a significant change to our build process. We have automated tests ready to run on other architectures, gating publication to the edge channel. But build.snapcraft.io unfortunately doesn't support CI gating, so right now we have to choose between CI/CD and multiple architecture support. More details here: https://forum.snapcraft.io/t/launchpad-post-build-pre-upload-testing/5545

Changed in usd-importer:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: snap
Robie Basak (racb)
summary: - git-ubuntu unavailble on arm64
+ git-ubuntu unavailble on non-amd64 architectures
summary: - git-ubuntu unavailble on non-amd64 architectures
+ git-ubuntu unavailable on non-amd64 architectures
Revision history for this message
Loïc Minier (lool) wrote :

Hi Robie, I don't think the situation has changed in terms of snapcraft or LP features around snap package pre-upload testing; may I suggest one of the following strategies to unblock this:

1) uploading but not releasing/publishing new snap builds to the edge channel until they are tested (need to run the test outside of Launchpad, snap download --revision should work if logged in)

2) uploading and releasing to edge channel, testing immediately afterwards, rolling back the edge channel to previous published in case of regressions (this window would be short, and it's edge after all)

3) testing of the prime/ directory triggered as a post-build step of the last snapcraft part

4) upload of the snap from your CI/CD instead of the one from Launchpad

5) upload to a branch of edge (channel), run the tests outside of Launchpad, then promote to edge

I haven't tested these options, and I don't see the current non-LP CI/CD (in Travis IIUC?), so not sure how easy it is, but 5) might be relatively short to implement; perhaps 3) is also relatively straightforward and requires less CI/CD config changes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.