You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the reference-browser decision image tagged, but not pinned to a sha. We used to have a sha allowlist, and then removed that in favor of the sha being in the gecko .taskcluster.yml. We should probably enforce having a sha here.
There are actually three docker shas: the compressed artifact sha, and then docker has 2 different shas for an image: one with metadata and one without, iirc. I believe we want this one, but we should verify:
We have the reference-browser decision image tagged, but not pinned to a sha. We used to have a sha allowlist, and then removed that in favor of the sha being in the gecko .taskcluster.yml. We should probably enforce having a sha here.
There are actually three docker shas: the compressed artifact sha, and then docker has 2 different shas for an image: one with metadata and one without, iirc. I believe we want this one, but we should verify:
from here. Also see https://stackoverflow.com/questions/42879587/what-does-each-sha-mean-in-a-docker-image
Order of operations:
The text was updated successfully, but these errors were encountered: