Commit 9e14ebe6 authored by Lin Jen-Shin's avatar Lin Jen-Shin

Update CHANGELOG and doc for locked runner feature

parent 7fa80a79
...@@ -39,6 +39,7 @@ v 8.9.0 (unreleased) ...@@ -39,6 +39,7 @@ v 8.9.0 (unreleased)
- Projects pending deletion will render a 404 page - Projects pending deletion will render a 404 page
- Measure queue duration between gitlab-workhorse and Rails - Measure queue duration between gitlab-workhorse and Rails
- Make authentication service for Container Registry to be compatible with < Docker 1.11 - Make authentication service for Container Registry to be compatible with < Docker 1.11
- Make it possible to lock a runner from being enabled for other projects
- Add Application Setting to configure Container Registry token expire delay (default 5min) - Add Application Setting to configure Container Registry token expire delay (default 5min)
- Cache assigned issue and merge request counts in sidebar nav - Cache assigned issue and merge request counts in sidebar nav
- Use Knapsack only in CI environment - Use Knapsack only in CI environment
......
...@@ -96,6 +96,12 @@ To register the runner, run the command below and follow instructions: ...@@ -96,6 +96,12 @@ To register the runner, run the command below and follow instructions:
sudo gitlab-runner register sudo gitlab-runner register
``` ```
### Lock a specific runner from being enabled from other projects
You can configure a runner to prevent it from being enabled for the other
projects, so it's exclusive to current projects. This setting is available
on each runner in *Project Settings* > *Runners*.
### Making an existing Shared Runner Specific ### Making an existing Shared Runner Specific
If you are an admin on your GitLab instance, If you are an admin on your GitLab instance,
......
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