diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-10 15:10:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-10 15:10:09 +0300 |
| commit | c68905777ea271aea120a58d2d1246e84aea4264 (patch) | |
| tree | 55064d8892d91fe0cad6c29a5e042778b1f23c68 /doc/ci/environments | |
| parent | 67b0b1c43f3d705b92f62ef231dfce1d7f3c0a30 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/environments')
| -rw-r--r-- | doc/ci/environments/deployment_safety.md | 2 | ||||
| -rw-r--r-- | doc/ci/environments/index.md | 2 | ||||
| -rw-r--r-- | doc/ci/environments/protected_environments.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/environments/deployment_safety.md b/doc/ci/environments/deployment_safety.md index 6fda6bb0d8b..86e004322bc 100644 --- a/doc/ci/environments/deployment_safety.md +++ b/doc/ci/environments/deployment_safety.md @@ -117,7 +117,7 @@ The other pipelines don't get the protected variable. You can also [scope variables to specific environments](../variables/where_variables_can_be_used.md#variables-with-an-environment-scope). We recommend that you use protected variables on protected environments to make sure that the secrets aren't exposed unintentionally. You can also define production secrets on the -[runner side](../runners/README.md#prevent-runners-from-revealing-sensitive-information). +[runner side](../runners/configure_runners.md#prevent-runners-from-revealing-sensitive-information). This prevents other maintainers from reading the secrets and makes sure that the runner only runs on protected branches. diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md index 8ed35bf8bfd..a60c0d03e8f 100644 --- a/doc/ci/environments/index.md +++ b/doc/ci/environments/index.md @@ -409,7 +409,7 @@ The job with [`action: stop` might not run](#the-job-with-action-stop-doesnt-run if it's in a later stage than the job that started the environment. If you can't use [pipelines for merge requests](../merge_request_pipelines/index.md), -set the [`GIT_STRATEGY`](../runners/README.md#git-strategy) to `none` in the +set the [`GIT_STRATEGY`](../runners/configure_runners.md#git-strategy) to `none` in the `stop_review` job. Then the [runner](https://docs.gitlab.com/runner/) doesn't try to check out the code after the branch is deleted. diff --git a/doc/ci/environments/protected_environments.md b/doc/ci/environments/protected_environments.md index a6c9e4bd38e..c276059cb9e 100644 --- a/doc/ci/environments/protected_environments.md +++ b/doc/ci/environments/protected_environments.md @@ -215,7 +215,7 @@ configured: (or above) to the top-level group. They can maintain CI/CD configurations for the higher environments (such as production) in the group-level settings page, wnich includes group-level protected environments, - [group-level runners](../runners/README.md#group-runners), + [group-level runners](../runners/runners_scope.md#group-runners), [group-level clusters](../../user/group/clusters/index.md), etc. Those configurations are inherited to the child projects as read-only entries. This ensures that only operators can configure the organization-wide |