BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
76c72363
Commit
76c72363
authored
May 09, 2018
by
Achilleas Pipinellis
Committed by
Filipa Lacerda
May 09, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Merge branch '10244-group-runner-docs' into 'master'
Add docs for group runners Closes #10244 See merge request gitlab-org/gitlab-ce!18807
parent
63001125
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
3 deletions
+14
-3
README.md
doc/ci/runners/README.md
+14
-3
No files found.
doc/ci/runners/README.md
View file @
76c72363
...
...
@@ -11,7 +11,7 @@ Ideally, the GitLab Runner should not be installed on the same machine as GitLab
Read the
[
requirements documentation
](
../../install/requirements.md#gitlab-runner
)
for more information.
## Shared
vs specific
Runners
## Shared
, specific and group
Runners
After
[
installing the Runner
][
install
]
, you can either register it as shared or
specific. You can only register a shared Runner if you have admin access to
...
...
@@ -32,6 +32,9 @@ are:
Runners. For example, if you want to deploy a certain project, you can setup
a specific Runner to have the right credentials for this. The
[
usage of tags
](
#using-tags
)
may be useful in this case. Specific Runners process jobs using a
[
FIFO
]
queue.
-
**Group Runners**
are useful when you have multiple projects under one group
and would like all projects to have access to a set of Runners. Group Runners
process jobs using a
[
FIFO
]
queue.
A Runner that is specific only runs for the specified project(s). A shared Runner
can run jobs for every project that has enabled the option
**Allow shared Runners**
...
...
@@ -66,7 +69,7 @@ Runners to disabled.
## Registering a specific Runner
Registering a specific can be done in two ways:
Registering a specific
Runner
can be done in two ways:
1.
Creating a Runner with the project registration token
1.
Converting a shared Runner into a specific Runner (one-way, admin only)
...
...
@@ -79,6 +82,14 @@ visit the project you want to make the Runner work for in GitLab:
1.
Go to
**Settings > CI/CD**
to obtain the token
1.
[
Register the Runner
][
register
]
## Registering a group Runner
Creating a group Runner requires Master permissions for the group. To create a
group Runner visit the group you want to make the Runner work for in GitLab:
1.
Go to
**Settings > CI/CD**
to obtain the token
1.
[
Register the Runner
][
register
]
### Making an existing shared Runner specific
If you are an admin on your GitLab instance, you can turn any shared Runner into
...
...
@@ -121,7 +132,7 @@ To enable/disable a Runner in your project:
> **Note**:
Consider that if you don't lock your specific Runner to a specific project, any
user with Master role in you project can assign your
r
unner to another arbitrary
user with Master role in you project can assign your
R
unner to another arbitrary
project without requiring your authorization, so use it with caution.
An admin can enable/disable a specific Runner for projects:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment