Closed
Bug 902256
Opened 11 years ago
Closed 11 years ago
Telemetry Dashboard should update when new code is pushed
Categories
(Infrastructure & Operations :: IT-Managed Tools, task, P4)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lonnen, Unassigned)
References
Details
The Telemetry Dashboard production site seems to wait until an overnight run of the M/R job to update the production site. When new code is pushed, it should go live immediately without waiting for the next M/R job or needing to run a new one. This means clearing out everything but the html/data directory, and then copying the html directory from the new repository into the production dir. Something like: ``` find html/* | grep -v "$html/data" | xargs rm -rf; cp -r ~/telemetry-dashboard/html/ html; ```
Comment 1•11 years ago
|
||
i manually kicked off the same process the daily cron runs: $ cd ~telemetrydash/telemetry-dashboard; git pull && ./script/bootstrap
Reporter | ||
Comment 2•11 years ago
|
||
Thanks Cturra. Sounds like I'm after a more frequent cron that just runs: `cd ~telemetrydash/telemetry-dashboard; git pull` Maybe every 10 or 15 minutes?
Comment 3•11 years ago
|
||
(In reply to Chris Lonnen :lonnen from comment #2) > Thanks Cturra. Sounds like I'm after a more frequent cron that just runs: > > `cd ~telemetrydash/telemetry-dashboard; git pull` > > Maybe every 10 or 15 minutes? Hi :lonnen, As per your instructions when we first set the site up, the following cron job gets run four times per hour : --- cd /data/static/src/telemetry-dash.mozilla.org/telemetrydash; git pull -q && /data/static/deploy telemetry-dash.mozilla.org > /dev/null 2>&1 --- Is this not acceptable ?
Component: Server Operations: Web Operations → WebOps: IT-Managed Tools
Flags: needinfo?(chris.lonnen)
Priority: -- → P4
Product: mozilla.org → Infrastructure & Operations
Reporter | ||
Comment 4•11 years ago
|
||
That works for me. I should have checked mana before filing.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(chris.lonnen)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•