| Summary: | Shut down dash.eclipse.org | ||
|---|---|---|---|
| Product: | Community | Reporter: | Denis Roy <denis.roy> |
| Component: | Dashboard | Assignee: | Portal Bugzilla Dummy Inbox <portal-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | 2017-Q2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 465708 | ||
| Bug Blocks: | 514734 | ||
|
Description
Denis Roy
I will propose we schedule the shutdown of the old dash.eclipse.org on Dec. 21, 2015 and focus our current energies on implementing old dash functionality that we want to maintain (before implementing new functionality). I've added a deprecated banner to some of the dash.eclipse.org pages. Note that the "dashboard" database is used by some other processes that gather commit data. Does the dashboard database go away with Dash? I am going under the assumption that gathering commit data is old functionality we want to preserve moving forward. I've got a bunch of stuff running on the dashboard database. I'd like to keep that database around for the foreseeable future. I'm confident that I've shut down everything other than dash.eclipse.org itself that uses the "commits" and "commits_index" tables. The dash.eclipse.org server itself can be shut down at your convenience. Please set up a permanent redirect to eclipse.bitergia.io. In some cron somewhere, there should be a script that pulls updates from a Dash project Git repository [1] and calls the run-batch.sh script [2]. This can be shut down (chances are shutting down dash.eclipse.org will shut this down as well anyway). [1] http://git.eclipse.org/c/dash/org.eclipse.dash.dashboard.git/ [2] ./commits/batch/run-batch.sh AFAICT, the old dash.eclipse.org is not accessible. I think that we're done here. Correct me if I'm wrong. |