Graph and monitor Linux .deb / .rpm installer sizes |
||||
Issue description
The Google Chrome Linux x64 bot [1] generates 6 Linux installer packages:
{ .deb, .rpm } x { stable, beta, unstable (AKA dev) }
We currently don't graph their sizes, but we should, like we do for Windows with mini_installer.exe. Given there are 6 packages, we don't have to monitor them all. I would recommend just monitoring the stable channel .deb and .rpm. It is slightly tricky, as the file name is not fixed. Sample filenames are google-chrome-stable_62.0.3165.0-1_amd64.deb and google-chrome-stable_62.0.3165.0-1.x86_64.rpm.
Once we have a graph, then we can start monitoring the sizes and look for regressions.
[1] https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux%20x64
,
Sep 22 2017
We had a regression with bug 767521. It affects Linux and ChromeOS, and only got caught on the ChromeOS side.
,
Dec 11 2017
And for M64, we have bug 793991 . Can someone comment on what the process is for adding graphs?
,
Dec 12 2017
,
Dec 12
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 12
|
||||
►
Sign in to add a comment |
||||
Comment 1 by benhenry@chromium.org
, Aug 25 2017Status: Available (was: Untriaged)