mirror of
https://ops.gitlab.net/gitlab-org/gitlab-build-images.git
synced 2025-12-12 19:42:55 +01:00
Cache Google Chrome deb with generic packages rather than AWS
We currently cache Google Chrome deb files in AWS. Since GitLab 14.8 Generic Packages have become generally available. So in order to remove the dependency on AWS and to dogfood the feature, we are going to cache the Google Chrome deb files with GitLab https://docs.gitlab.com/ee/user/packages/generic_packages/
This commit is contained in:
parent
6bb7cc091f
commit
a9c5fa7b10
4 changed files with 37 additions and 30 deletions
|
|
@ -83,10 +83,10 @@ unexpectedly. For reference, this happened in the past: https://gitlab.com/gitla
|
|||
|
||||
Google has a policy of yanking older versions of Google Chrome from their PPA
|
||||
whenever a new major version is released. To help maintain consistent build
|
||||
images, there is a CI step that saves the latest Google Chrome .deb into an S3
|
||||
bucket. The install for Chrome will attempt to retrieve from the bucket if it
|
||||
cannot find the file in the apt repository. See `scripts/cache-google-chrome`
|
||||
for more details.
|
||||
images, there is a CI step that saves the latest Google Chrome .deb into an the
|
||||
GitLab package registry. The install for Chrome will attempt to retrieve from the
|
||||
registry if it cannot find the file in the apt repository.
|
||||
See `scripts/cache-google-chrome` for more details.
|
||||
|
||||
## Contributing
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue