NcamGnrvngu/gitlab-build-images
1
0
Fork 0
mirror of https://ops.gitlab.net/gitlab-org/gitlab-build-images.git synced 2025-12-09 10:02:56 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Use a manual job to trigger a selective build/push

Browse source
This commit is contained in:
Kamil Trzciński 2021-02-02 13:30:18 +01:00
parent a9204d345d
commit 3acad93b15
4 changed files with 34 additions and 61 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -66,17 +66,13 @@ the name would be `ruby-2.4-golang-1.9-git-2.14`.
1. Add a test task: `ruby-2.4-golang-1.9-git-2.14 test: *test_custom`
1. Add a new build task: `ruby-2.4-golang-1.9-git-2.14: *build_and_deploy_custom`
#### Forcing custom images to be rebuilt
#### Pushing a rebuild image
By default, once a custom image is built, tagged and pushed to the registry, it's
not rebuilt to ensure an upstream dependency doesn't end up breaking our images
unexpectedly.
To build (or rebuild) a given image and push it, you need to enable manual action for a given
job after it is merged to master.
For reference, this happened in the past: https://gitlab.com/gitlab-org/gitlab/issues/205192
In the rare case where the `Dockerfile.custom` file is updated and all custom
images shoulld be rebuild, you can start a new pipeline and set the variable
`FORCE_BUILD` to `true`.
By default we don't do it to ensure that an upstream dependency doesn't end up breaking our images
unexpectedly. For reference, this happened in the past: https://gitlab.com/gitlab-org/gitlab/issues/205192
## Note regarding Google Chrome