Commit 4244579a authored by Achilleas Pipinellis's avatar Achilleas Pipinellis 🚀

Merge branch 'docs-update-ce-links-to-ee' into 'master'

Updating Docs links from /ce to /ee

See merge request gitlab-org/gitlab-runner!1061
parents 0d1ba559 0b6b5906
......@@ -68,7 +68,7 @@ be repeated after all requests for the other workers + their sleeps are called.
The section `[session_server]` is a system runner level configuration, so it should be specified at the root level,
not per executor i.e. it should be outside `[[runners]]` section. The session server allows the user to interact
with jobs that the Runner is responsible for. A good example of this is the
[interactive web terminal](https://docs.gitlab.com/ce/ci/interactive_web_terminal).
[interactive web terminal](https://docs.gitlab.com/ee/ci/interactive_web_terminal).
Both `listen_address` and `advertise_address` should be provided in the form
of `host:port`, where `host` may be an IP address (e.g., `127.0.0.1:8093`)
......@@ -736,9 +736,10 @@ It depends on what you'd like to do.
[TOML]: https://github.com/toml-lang/toml
[Docker Engine]: https://docs.docker.com/engine/
[yaml-priv-reg]: https://docs.gitlab.com/ce/ci/yaml/README.html#image-and-services
[ci-build-permissions-model]: https://docs.gitlab.com/ce/user/project/new_ci_build_permissions_model.html
[yaml-priv-reg]: https://docs.gitlab.com/ee/ci/yaml/README.html#image-and-services
[ci-build-permissions-model]: https://docs.gitlab.com/ee/user/project/new_ci_build_permissions_model.html
[secpull]: ../security/index.md#usage-of-private-docker-images-with-if-not-present-pull-policy
[priv-example]: https://docs.gitlab.com/ce/ci/docker/using_docker_images.html#define-an-image-from-a-private-docker-registry
[variable]: https://docs.gitlab.com/ce/ci/variables/#variables
[priv-example]: https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#define-an-image-from-a-private-container-registry
[variable]: https://docs.gitlab.com/ee/ci/variables/#variables
[cronvendor]: https://github.com/gorhill/cronexpr#implementation
......@@ -152,7 +152,7 @@ about all the options you can use under `[[runners]]`.
In the `[runners.docker]` section you can define the default Docker image to
be used by the child Runners if it's not defined in [`.gitlab-ci.yml`](https://docs.gitlab.com/ee/ci/yaml/).
By using `privileged = true`, all Runners will be able to run
[Docker in Docker](https://docs.gitlab.com/ce/ci/docker/using_docker_build.html#use-docker-in-docker-executor)
[Docker in Docker](https://docs.gitlab.com/ee/ci/docker/using_docker_build.html#use-docker-in-docker-executor)
which is useful if you plan to build your own Docker images via GitLab CI/CD.
Next, we use `disable_cache = true` to disable the Docker executor's inner
......
......@@ -115,4 +115,4 @@ Supported systems for interactive web terminals by different shells:
| OSX | ✓ | ✗ | ✗ |
| FreeBSD | ✓ | ✗ | ✗ |
[services]: https://docs.gitlab.com/ce/ci/services/README.html
[services]: https://docs.gitlab.com/ee/ci/services/README.html
......@@ -317,7 +317,7 @@ to volume's mount path) where _secret's_ value should be saved. When using `item
There are a couple of caveats when using docker in your builds while running on
a kubernetes cluster. Most of these issues are already discussed in the
[**Using Docker Build**](https://docs.gitlab.com/ce/ci/docker/using_docker_build.html)
[**Using Docker Build**](https://docs.gitlab.com/ee/ci/docker/using_docker_build.html)
section of the gitlab-ci
documentation but it is worth it to revisit them here as you might run into
some slightly different things when running this on your cluster.
......
......@@ -8,7 +8,7 @@ Before registering a Runner, you need to first:
- [Install it](../install/index.md) on a server separate than where GitLab
is installed on
- [Obtain a token](https://docs.gitlab.com/ce/ci/runners/) for a shared or
- [Obtain a token](https://docs.gitlab.com/ee/ci/runners/) for a shared or
specific Runner via GitLab's interface
## GNU/Linux
......@@ -329,4 +329,4 @@ docker run --rm -t -i -v /path/to/config:/etc/gitlab-runner --name gitlab-runner
--locked="false"
```
[tags]: https://docs.gitlab.com/ce/ci/runners/#using-tags
[tags]: https://docs.gitlab.com/ee/ci/runners/#using-tags
......@@ -218,4 +218,4 @@ Some documentation tips:
> need at least GitLab Runner v1.7.0 (not released yet) to work.
[runner-milestones]: https://gitlab.com/gitlab-org/gitlab-runner/milestones
[issue closing pattern]: https://docs.gitlab.com/ce/user/project/issues/automatic_issue_closing.html
[issue closing pattern]: https://docs.gitlab.com/ee/user/project/issues/automatic_issue_closing.html
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