Provide your GitLab Runner (to be installed next) with your certs by
Provide your GitLab Runner (to be installed next) with your certs by
[following the steps for using trusted certificates with your Runner](https://docs.gitlab.com/runner/install/docker.html#installing-trusted-ssl-server-certificates):
[following the steps for using trusted certificates with your runner](https://docs.gitlab.com/runner/install/docker.html#installing-trusted-ssl-server-certificates):
| **{overview}**[Overview](#overview-section) | View your GitLab [Dashboard](#admin-dashboard), and administer [projects](#administering-projects), [users](#administering-users), [groups](#administering-groups), [jobs](#administering-jobs), [Runners](#administering-runners), and [Gitaly servers](#administering-gitaly-servers). |
| **{overview}**[Overview](#overview-section) | View your GitLab [Dashboard](#admin-dashboard), and administer [projects](#administering-projects), [users](#administering-users), [groups](#administering-groups), [jobs](#administering-jobs), [runners](#administering-runners), and [Gitaly servers](#administering-gitaly-servers). |
| **{monitor}** Monitoring | View GitLab [system information](#system-info), and information on [background jobs](#background-jobs), [logs](#logs), [health checks](monitoring/health_check.md), [requests profiles](#requests-profiles), and [audit logs](#audit-log). |
| **{monitor}** Monitoring | View GitLab [system information](#system-info), and information on [background jobs](#background-jobs), [logs](#logs), [health checks](monitoring/health_check.md), [requests profiles](#requests-profiles), and [audit logs](#audit-log). |
| **{messages}** Messages | Send and manage [broadcast messages](broadcast_messages.md) for your users. |
| **{messages}** Messages | Send and manage [broadcast messages](broadcast_messages.md) for your users. |
| **{hook}** System Hooks | Configure [system hooks](../../system_hooks/system_hooks.md) for many events. |
| **{hook}** System Hooks | Configure [system hooks](../../system_hooks/system_hooks.md) for many events. |
...
@@ -196,51 +196,51 @@ For each job, the following details are listed:
...
@@ -196,51 +196,51 @@ For each job, the following details are listed:
| Timing | Duration of the job, and how long ago the job completed. |
| Timing | Duration of the job, and how long ago the job completed. |
| Coverage | Percentage of tests coverage. |
| Coverage | Percentage of tests coverage. |
### Administering Runners
### Administering runners
You can administer all Runners in the GitLab instance from the Admin Area's **Runners** page. See
You can administer all runners in the GitLab instance from the Admin Area's **Runners** page. See
[GitLab Runner](https://docs.gitlab.com/runner/) for more information on Runner itself.
[GitLab Runner](https://docs.gitlab.com/runner/) for more information.
To access the **Runners** page, go to **Admin Area > Overview > Runners**.
To access the **Runners** page, go to **Admin Area > Overview > Runners**.
The **Runners** page features:
The **Runners** page features:
- A description of Runners, and their possible states.
- A description of runners and their possible states.
- Instructions on installing a Runner.
- Instructions on installing a runner.
- A list of all registered Runners.
- A list of all registered runners.
Runners are listed in descending order by the date they were created, by default. You can change
Runners are listed in descending order by the date they were created, by default. You can change
the sort order to *Last Contacted* from the dropdown beside the search field.
the sort order to *Last Contacted* from the dropdown beside the search field.
To search Runners' descriptions:
To search runners' descriptions:
1. In the **Search or filter results...** field, type the description of the Runner you want to
1. In the **Search or filter results...** field, type the description of the runner you want to
find.
find.
1. Press Enter.
1. Press Enter.
You can also filter Runners by status, type, and tag. To filter:
You can also filter runners by status, type, and tag. To filter:
1. Click in the **Search or filter results...** field.
1. Click in the **Search or filter results...** field.
1. Select **status:**, **type:**, or **tag:**.
1. Select **status:**, **type:**, or **tag:**.
1. Select or enter your search criteria.
1. Select or enter your search criteria.
For each Runner, the following attributes are listed:
For each runner, the following attributes are listed:
| Attribute | Description |
| Attribute | Description |
| ------------ | ----------- |
| ------------ | ----------- |
| Type | One or more of the following states: shared, group, specific, locked, or paused |
| Type | One or more of the following states: shared, group, specific, locked, or paused |
| Runner token | Token used to identify the Runner, and which the Runner uses to communicate with the GitLab instance |
| Runner token | Token used to identify the runner, and which the runner uses to communicate with the GitLab instance |
| Description | Description given to the Runner when it was created |
| Description | Description given to the runner when it was created |
| Version | GitLab Runner version |
| Version | GitLab Runner version |
| IP address | IP address of the host on which the Runner is registered |
| IP address | IP address of the host on which the runner is registered |
| Projects | Projects to which the Runner is assigned |
| Projects | Projects to which the runner is assigned |
| Jobs | Total of jobs run by the Runner |
| Jobs | Total of jobs run by the runner |
| Tags | Tags associated with the Runner |
| Tags | Tags associated with the runner |
| Last contact | Timestamp indicating when the GitLab instance last contacted the Runner |
| Last contact | Timestamp indicating when the GitLab instance last contacted the runner |
# Continuous Integration and Deployment Admin settings **(CORE ONLY)**
# Continuous Integration and Deployment Admin settings **(CORE ONLY)**
In this area, you will find settings for Auto DevOps, Runners, and job artifacts.
In this area, you will find settings for Auto DevOps, runners, and job artifacts.
You can find it in the **Admin Area > Settings > CI/CD**.
You can find it in the **Admin Area > Settings > CI/CD**.
...
@@ -86,13 +86,13 @@ be updated for artifacts created before this setting was changed.
...
@@ -86,13 +86,13 @@ be updated for artifacts created before this setting was changed.
The administrator may need to manually search for and expire previously-created
The administrator may need to manually search for and expire previously-created
artifacts, as described in the [troubleshooting documentation](../../../administration/troubleshooting/gitlab_rails_cheat_sheet.md#remove-artifacts-more-than-a-week-old).
artifacts, as described in the [troubleshooting documentation](../../../administration/troubleshooting/gitlab_rails_cheat_sheet.md#remove-artifacts-more-than-a-week-old).
