mirror of
https://ops.gitlab.net/gitlab-org/gitlab-build-images.git
synced 2025-12-09 10:02:56 +01:00
Add an image for git v2.16 and Chrome v63
Also adds a caching mechanism for storing the latest version in an S3 bucket.
This commit is contained in:
parent
aec5d3edbd
commit
34ce2513c8
5 changed files with 80 additions and 11 deletions
14
README.md
14
README.md
|
|
@ -63,14 +63,12 @@ the name would be `ruby-2.4-golang-1.9-git-2.14`.
|
|||
|
||||
# Note regarding Google Chrome
|
||||
|
||||
Google has a policy of yanking older versions of Google Chrome from their PPA whenever a new major
|
||||
version is released. This means images with non-current chrome versions will fail to build. Until
|
||||
a better solution is worked out, we will remove images based on older Chrome versions from the build
|
||||
process, but preserve them for reference within a comment in the `.gitlab-ci.yml` file.
|
||||
|
||||
These images will persist in the docker repository for legacy use, but will no longer be recompiled.
|
||||
If an update ever needs to be made to an image containing an older version of Chrome, a workaround
|
||||
can be modeled after https://gitlab.com/gitlab-org/gitlab-build-images/merge_requests/54
|
||||
Google has a policy of yanking older versions of Google Chrome from their PPA
|
||||
whenever a new major version is released. To help maintain consistant 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.
|
||||
|
||||
# Contributing
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue