Follow-up from "Updating more release content to match standards"
The following discussion from !73781 (merged) should be addressed:
-
@marcel.amirault started a discussion: (+2 comments) The reason I rephrased your original submission to what's here currently is because it's not exclusive to the Docker and Shell executors. The original text just listed two options (docker image, or shell runner with
release-cli
), but didn't say these two executors were the only options: https://docs.gitlab.com/14.4/ee/ci/yaml/index.html#release-cli-docker-imageThe main point is just that the job needs to access the
release-cli
, so if you don't use the Docker image, install it on the runner. So how about something along these lines (which will make this section much smaller)?The release job must have access to the [`release-cli`](https://gitlab.com/gitlab-org/release-cli/-/tree/master/docs). If you use the [Shell executor](https://docs.gitlab.com/runner/executors/shell.html), [install `release-cli`](../../user/project/releases/release_cli.md) on the server where the runner is registered. Otherwise, you can use this Docker image from the GitLab Container Registry: ```yaml image: registry.gitlab.com/gitlab-org/release-cli:latest` ```
Or, in list style?
The release job must have access to the [`release-cli`](https://gitlab.com/gitlab-org/release-cli/-/tree/master/docs): - If you use the [Shell executor](https://docs.gitlab.com/runner/executors/shell.html), [install `release-cli`](../../user/project/releases/release_cli.md) on the server where the runner is registered. - For other executors, you can use this Docker image from the GitLab Container Registry: ```yaml image: registry.gitlab.com/gitlab-org/release-cli:latest` ```