debian-mirror-gitlab/doc/user/project/integrations/services_templates.md

68 lines
2.7 KiB
Markdown
Raw Normal View History

2020-10-24 23:57:45 +05:30
---
stage: Create
group: Ecosystem
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-24 23:57:45 +05:30
---
2021-04-17 20:07:23 +05:30
# Service templates **(FREE)**
2017-08-17 22:00:37 +05:30
2021-03-11 19:13:27 +05:30
WARNING:
Service templates are [deprecated and scheduled to be removed](https://gitlab.com/gitlab-org/gitlab/-/issues/268032)
in GitLab 14.0. Use [project integration management](#central-administration-of-project-integrations) instead.
2021-01-03 14:25:43 +05:30
Using a service template, GitLab administrators can:
2020-07-28 23:09:34 +05:30
2021-01-03 14:25:43 +05:30
- Provide default values for configuring integrations when creating new projects.
- Bulk configure all existing projects in one step.
2020-07-28 23:09:34 +05:30
2021-01-03 14:25:43 +05:30
When you enable a service template:
- The defaults are applied to **all** existing projects that either:
- Don't already have the integration enabled.
- Don't have custom values stored for already enabled integrations.
- Values are populated on each project's configuration page for the applicable
integration.
- Settings are stored at the project level.
If you disable the template:
- GitLab default values again become the default values for integrations on
new projects.
2021-02-22 17:27:13 +05:30
- Projects previously configured using the template continue to use those settings.
2021-01-03 14:25:43 +05:30
If you change the template, the revised values are applied to new projects. This feature
does not provide central administration of integration settings.
## Central administration of project integrations
A new set of features is being introduced in GitLab to provide more control over
2021-04-29 21:17:54 +05:30
how integrations are configured at the instance, group, and project level. For
more information, read more about:
2021-01-03 14:25:43 +05:30
2021-04-29 21:17:54 +05:30
- [Setting up project integration management](../../admin_area/settings/project_integration_management.md) (introduced in GitLab 13.3)
- [Our plans for managing integrations](https://gitlab.com/groups/gitlab-org/-/epics/2137).
2017-08-17 22:00:37 +05:30
## Enable a service template
2020-03-13 15:44:24 +05:30
Navigate to the **Admin Area > Service Templates** and choose the service
template you wish to create.
2017-08-17 22:00:37 +05:30
2021-01-03 14:25:43 +05:30
Recommendation:
- Test the settings on some projects individually before enabling a template.
- Copy the working settings from a project to the template.
There is no "Test settings" option when enabling templates. If the settings do not work,
2021-02-22 17:27:13 +05:30
these incorrect settings are applied to all existing projects that do not already have
2021-01-03 14:25:43 +05:30
the integration configured. Fixing the integration then needs to be done project-by-project.
2020-07-28 23:09:34 +05:30
## Service for external issue trackers
2017-08-17 22:00:37 +05:30
2020-07-28 23:09:34 +05:30
The following image shows an example service template for Redmine.
2017-08-17 22:00:37 +05:30
![Redmine service template](img/services_templates_redmine_example.png)
2021-02-22 17:27:13 +05:30
For each project, you still need to configure the issue tracking
2017-08-17 22:00:37 +05:30
URLs by replacing `:issues_tracker_id` in the above screenshot with the ID used
2020-07-28 23:09:34 +05:30
by your external issue tracker.