You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using your own gitlab instance, the provided .gitlab-ci.yml will be automatically be using the settings provided by the GitLab Instance. If needed several options can be overriden.
3
+
When using your own GitLab instance, the provided .gitlab-ci.yml will automatically be using the settings provided by the GitLab instance. If needed, several options can be overriden.
4
4
5
5
Overrides for these values can be set within the project, under `Settings` -> `CI/CD` -> `Variables`.
6
6
@@ -9,4 +9,4 @@ Overrides for these values can be set within the project, under `Settings` -> `C
9
9
|`CI_REGISTRY`|`hub.docker.com`| If available this will be automatically overriden by registry address which is configured within the GitLab instance |
10
10
|`CI_REGISTRY_USER`|`gitlab-ci-token`| Username for the registry |
11
11
|`CI_REGISTRY_PASSWORD`|`${CI_JOB_TOKEN}`| Password for the registry |
12
-
|`DOCKER_IMAGE`|`sameersbn/gitlab`| Docker image name, will be automatically be overriden by the running GitLab instance with the `${CI_PROJECT_PATH}` variable. This will case the image to be uploaded to the local registry of the project within GitLab. |
12
+
|`DOCKER_IMAGE`|`sameersbn/gitlab`| Docker image name, will automatically be overriden by the running GitLab instance with the `${CI_PROJECT_PATH}` variable. This will cause the image to be uploaded to the local registry of the project within GitLab. |
0 commit comments