Closed Bug 1833603 Opened 3 years ago Closed 3 years ago

firefox release pipeline relies on net-mozaws-{prod,stage}-delivery-* s3 buckets

Categories

(Release Engineering :: Release Automation, task)

Tracking

(firefox-esr102 fixed, firefox113 wontfix, firefox114 wontfix, firefox115 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr102 --- fixed
firefox113 --- wontfix
firefox114 --- wontfix
firefox115 --- fixed

People

(Reporter: jcristau, Assigned: jcristau)

References

Details

Attachments

(3 files, 1 obsolete file)

We've moved archive.mozilla.org to be backed by gcs buckets so tasks need to stop relying on downloading from the s3 buckets directly.

Type: defect → task
Assignee: nobody → jcristau
Status: NEW → ASSIGNED
Keywords: leave-open
See Also: → 1833657
Attachment #9335228 - Attachment description: Bug 1833603 - update snap repackage task to download from archive.m.o instead of s3 buckets directly. r?#releng → Bug 1833603 - update snap repackage task to download from archive.m.o instead of s3 buckets directly. r?#releng
Keywords: leave-open
Attachment #9334635 - Attachment is obsolete: true
Pushed by jcristau@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/837ef9e285bd use google cloud storage instead of amazon s3 for release-generate-checksums task. r=releng-reviewers,bhearsum DONTBUILD https://hg.mozilla.org/integration/autoland/rev/b8d6207023b9 update flatpak repackage task to download from archive.m.o instead of s3 buckets directly. r=releng-reviewers,bhearsum,hneiva DONTBUILD https://hg.mozilla.org/integration/autoland/rev/7d7efb2b73d4 update snap repackage task to download from archive.m.o instead of s3 buckets directly. r=releng-reviewers,bhearsum DONTBUILD

ni?self to request esr102 uplift after 115 is in beta

Flags: needinfo?(jcristau)

Comment on attachment 9335226 [details]
Bug 1833603 - use google cloud storage instead of amazon s3 for release-generate-checksums task. r?#releng

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: we'd like to stop uploading release artifacts to s3, and use gcs exclusively, but these tasks use the s3 buckets directly; this switches them to use archive.mozilla.org itself, or the corresponding gcs buckets.
  • User impact if declined: n/a
  • Fix Landed on Version: 115
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): No issues on beta since this landed.

I'll note the release-generate-checksums change will need a corresponding update for comm-esr102.

Flags: needinfo?(jcristau)
Attachment #9335226 - Flags: approval-mozilla-esr102?
Attachment #9335228 - Flags: approval-mozilla-esr102?

:rjl FYI about the comm-esr102 impact if/when this goes into mozilla-esr102.

Flags: needinfo?(rob)

Comment on attachment 9335226 [details]
Bug 1833603 - use google cloud storage instead of amazon s3 for release-generate-checksums task. r?#releng

Approved for 102.13esr.

Attachment #9335226 - Flags: approval-mozilla-esr102? → approval-mozilla-esr102+

Comment on attachment 9335228 [details]
Bug 1833603 - update snap repackage task to download from archive.m.o instead of s3 buckets directly. r?#releng

Approved for 102.13esr.

Attachment #9335228 - Flags: approval-mozilla-esr102? → approval-mozilla-esr102+

(In reply to Julien Cristau [:jcristau] from comment #12)

:rjl FYI about the comm-esr102 impact if/when this goes into mozilla-esr102.

danke.

Flags: needinfo?(rob)
Component: Release Automation: Uploading → Release Automation
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: