Commit 696f09c7 authored by Sean McGivern's avatar Sean McGivern

Merge branch 'patch-4' into 'master'

Improve docs on `gitlab-ci-token` user

See merge request !6002
parents 83736987 eecb52e1
...@@ -242,10 +242,10 @@ docker-in-docker on your runners, this is how your `.gitlab-ci.yml` could look: ...@@ -242,10 +242,10 @@ docker-in-docker on your runners, this is how your `.gitlab-ci.yml` could look:
- docker push registry.example.com/group/project:latest - docker push registry.example.com/group/project:latest
``` ```
You have to use the credentials of the special `gitlab-ci-token` user with its You have to use the special `gitlab-ci-token` user created for you in order to
password stored in `$CI_BUILD_TOKEN` in order to push to the Registry connected push to the Registry connected to your project. Its password is provided in the
to your project. This allows you to automate building and deployment of your `$CI_BUILD_TOKEN` variable. This allows you to automate building and deployment
Docker images. of your Docker images.
Here's a more elaborate example that splits up the tasks into 4 pipeline stages, Here's a more elaborate example that splits up the tasks into 4 pipeline stages,
including two tests that run in parallel. The build is stored in the container including two tests that run in parallel. The build is stored in the container
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment