1513296 - Pin a specific version of the snapcraft command

Status: RESOLVED WONTFIX

(Release Engineering Graveyard :: Release Automation: Snap, enhancement)

Description

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

Currently, the task for building the Firefox snap references snapcore's “stable” branch[1], but the upcoming 3.0 version is incompatible with our snapcraft.yaml; assuming that at some point in the future “stable” rolls over to 3.0, that would break our builds, including retroactively when trying to build older versions.

This would generally be a bad thing, but it seems especially bad if we want full CI integration (bug 1297531).

[1] https://searchfox.org/mozilla-central/rev/adcc169dcf58c2e45ba65c4ed5661d666fc3ac74/taskcluster/docker/firefox-snap/Dockerfile#1

Comment 1

[Johan Lorenzo [:jlorenzo]]

Thank you Jed for warning Releng! 

I wanted to quickly pin the hash on the image. It should have been a 10-minute-thing, but I ended up investigating bug 1513947.  Fixing that bug seems like a huge taskcluster project. We're then down to 2 solutions:
a. we ask the snapcraft team to provide a docker tag for snapcraft 2.x. Right now, they just provide: edge, beta, candidate, last-proposed, and release [1]
b. Or we port our snap builds to v3, which is likely be a bigger project. CC'ing jlund to warn about this potential breakage in the release pipeline.


[1] https://store.docker.com/community/images/snapcore/snapcraft/tags

Comment 2

[Johan Lorenzo [:jlorenzo]]

(In reply to Johan Lorenzo [:jlorenzo] from comment #1)
> a. we ask the snapcraft team to provide a docker tag for snapcraft 2.x.

See https://forum.snapcraft.io/t/expose-docker-tags-for-snapcraft-2-x/8980

Comment 3

[Johan Lorenzo [:jlorenzo]]

Per https://forum.snapcraft.io/t/expose-docker-tags-for-snapcraft-2-x/8980/7, this won't affect our automation. There is no further action needed then. Please reopen if something is wrong or missing.