Closed Bug 1831952 Opened 1 year ago Closed 1 year ago

migrate symbols server users to use symbols.mozilla.org

Categories

(Tecken :: General, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

The public symbols bucket is an AWS S3 bucket that's available via HTTP. It used to be the case that we encouraged users to use the bucket url directly rather than using symbols.mozilla.org and then having symbols.mozilla.org redirect to the final URL.

Now that we are planning to move the public symbols to a new place, we should look for users (taskcluster, build systems, analysis systems, etc) that reference the AWS S3 bucket directly and migrate them to use symbols.mozilla.org.

Oops--I tied this to the wrong project.

Blocks: 1687804
No longer blocks: 1812345

I did PRs for these:

For the gecko-dev ones, I think I need to make the change in moz-central. That change might need to be uplifted to the various channels including ESR so that when we do the GCP migration, we don't have to keep the AWS S3 bucket for 2 years.

I don't know what to do with the KaiOS B2G fork.

Gabriele: Am I right about what I need to do for the mozilla/gecko-dev instances? What should I do about updating the kaiostech/gecko-b2g repository? And/or should I talk with someone else about this?

Flags: needinfo?(gsvelto)

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #3)

For the gecko-dev ones, I think I need to make the change in moz-central. That change might need to be uplifted to the various channels including ESR so that when we do the GCP migration, we don't have to keep the AWS S3 bucket for 2 years.
[...]
Gabriele: Am I right about what I need to do for the mozilla/gecko-dev instances?

Yes, that's correct.

I don't know what to do with the KaiOS B2G fork.
[...]
What should I do about updating the kaiostech/gecko-b2g repository? And/or should I talk with someone else about this?

Let's ask Fabrice. I don't think they're being used though as I never managed to wire it up to automation.

Flags: needinfo?(gsvelto) → needinfo?(fabrice)

We don't use these symbols for KaiOS shipping builds since they have a different configuration and OEM specific additions. Feel free to do what's easiest from your side.

Flags: needinfo?(fabrice)
Summary: migrate symbols users to use symbols.mozilla.org → migrate symbols server users to use symbols.mozilla.org

This switches two scripts to use the Mozilla Symbols Server for downloading
symbols rather than accessing the AWS S3 bucket directly so they don't stop
working correctly when we move symbols from AWS to GCP.

Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/647d2166134d switch to use Mozilla Symbols Server. r=gsvelto
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

I landed the change for bhr_collection. gsvelto said that there's a scheduled task that runs via taskcluster which looks at the scripts in the nightly channel, so we don't need to uplift those changes to other channels.

The other changes I made aren't critical, so we're good here.

I also sent an email to stability and crash-reporting-wg mailing lists.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: