Closed Bug 1467854 Opened 6 years ago Closed 5 years ago

Decommission old Buildhub

Categories

(Cloud Services :: Operations: Miscellaneous, task)

Product:
Cloud Services
Component:
Operations: Miscellaneous
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1570028

People

(Reporter: peterbe, Unassigned)

References

Details

As of https://bugzilla.mozilla.org/show_bug.cgi?id=1467845 we have a new Buildhub service. It has its own URL which encompasses both the UI and the Elasticsearch proxy URL. Once that service is up and running healthily we should decommission the old Buildhub project and its operations. That includes... 1. The AWS Lambda function triggers on S3 Events on the S3 bucket for new releases. 2. The EC2 server that runs the daily cron job. 3. The UI website hosted on https://mozilla-services.github.io/buildhub/ 4. The Kinto servers a. https://buildhub.prod.mozaws.net/ b. https://buildhub.stage.mozaws.net/ 5. Archive https://github.com/mozilla-services/buildhub To make this easier; https://github.com/mozilla/buildhub2/issues/19 is about migrated the old URLs to work. Arguably, between launching the new Buildhub and decommission the old, there should be a grace period where we make sure the redirecting works as expected.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.