Closed Bug 1834541 Opened 2 years ago Closed 3 months ago

flatpak and snap repackages should get their artifacts from upstream tasks instead of archive.m.o's candidates dir

Categories

(Release Engineering :: General, enhancement)

Product:
Release Engineering
Component:
General
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: jcristau, Unassigned)

References

Details

The flatpak and snap repackages grab a firefox build and langpacks off of archive.mozilla.org. If they instead grabbed these files from the tasks that produce them (build or build-signing, and shippable-l10n-signing), they would be easier to test, and not depend on staging releases. I believe repackage-shippable-l10n-msix is a better model here.

Severity: -- → S3
QA Contact: jlorenzo

This was fixed for flatpak in bug 1726251, and the snap is not built in our CI nowadays.

Status: NEW → RESOLVED
Closed: 3 months ago
Depends on: 1726251
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.