Cache chromium for arm64 builds
What does this MR do and why?
- Cache chromium and chromium-driver for arm64 builds in addition to chrome
- Always install chrome or chromium from our own package registry to simplify scripts and reduce reliance on external systems
- Do not run cache chrome job in scope of every single mr pipeline, run on schedule and master push pipelines
Follow up:
We have a notification in quality slack channel to see if new version of chrome has been released. Might make sense to post explicitly to slack when a new version get's cached in package registry or even create update MR automatically
Edited by Andrejs Cunskis