Closed Bug 1229066 Opened 9 years ago Closed 9 years ago

Drop the job_eta tables after bug 1196764

Categories

(Tree Management :: Treeherder: Infrastructure, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

The old per-project job_eta tables are unused as of bug 1196764, so once we're happy that will stick (deployed on prod today), we can drop the tables.
Heroku: [~/src/treeherder]$ heroku run -- ./manage.py run_sql -s 'DROP TABLE job_eta;' Running ./manage.py run_sql -s "DROP TABLE job_eta;" on treeherder-heroku... up, run.6010 SQL command: DROP TABLE job_eta; 56 datasource found -------------------------- Sql code executed on mozilla-central: -------------------------- Sql code executed on mozilla-inbound: -------------------------- ...
Stage: [emorley@treeherder-rabbitmq1.stage.private.scl3 treeherder-service]$ ../venv/bin/python ./manage.py run_sql -s 'DROP TABLE job_eta;' SQL command: DROP TABLE job_eta; 70 datasource found -------------------------- Sql code executed on addon-sdk: -------------------------- Sql code executed on alder: -------------------------- Sql code executed on ash: ... Prod: [emorley@treeherder-rabbitmq1.private.scl3 treeherder-service]$ ../venv/bin/python ./manage.py run_sql -s 'DR OP TABLE job_eta;' SQL command: DROP TABLE job_eta; 76 datasource found -------------------------- Sql code executed on accessibility: -------------------------- Sql code executed on addon-sdk: -------------------------- ...
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.