Closed Bug 649054 Opened 15 years ago Closed 15 years ago

please insert the following into graphserver and staging-graphserver

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lsblakk, Assigned: fox2mike)

References

Details

Attachments

(1 file)

These branches need to be activated immediately for the branching to aurora tomorrow, so a bit more urgency on this one. Thank you.
Raising to blocker, as these need to be live in graphserver, and tested, before the code switchover from m-c to aurora happens tomorrow.
Severity: major → blocker
Assignee: server-ops → jdow
Assignee: jdow → justdave
Production is done. You appear to have three different staging sites now. Which URL is the app you want this applied to?
Apparently rhelmer knows....
Ya, sorry, I'm not sure which name is the one used by our staging but I think it's graphs2-stage?
Did someone confirm the right staging graphserver to update? I'm cc'ing Shyam too.
Graphserver staging is bm-buildgraph01.mozilla.org (graphs-stage.mozilla.org) For perfomatic 2.0 I've moved it to a new server (using the new staging domain graphs.allizom.org), that is on bm-graphs-stage01.mozilla.org They both connect to the same database server.
Just checked and somewhat confusingly, the database that graphs-stage.mozilla.org uses is graphs_stage2 (on tm-stage01-master01)
Done on stage.
Assignee: justdave → shyam
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: