Because the correlation script runs on a long-running instance, updating is a manual process. We've had a lot of confusion lately about which versions are running, since they are hardcoded into the script. If we used consul to put the version in the environment, we could modify the script to pull from the env. This would let us avoid updating the box. This is a hacky solution to make our current one less risky. If we can move this into application code or enable the box to update automatically it would obviate this.
I see it as a race :) Lonnen's idea is good. But it's completely moot if Lars finishes the new correlation script stuff in time. Perhaps we still use the old correlation scripts by the next release (end of Mozlando) so we can just vim edit the correlations one last time.
Is this still valid?
Dupe but too lazy to find the other bug. What we did, instead of introducing config, is to make the correlation cron script pull down the right Firefox versions from the crash-stats.mozilla.com/api/ProductVersions/ API.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.