10 KiB
| stage | group | info |
|---|---|---|
| Manage | Import and Integrate | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
Project integrations (FREE)
You can integrate your GitLab projects with other applications. Integrations are like plugins, and give you the freedom to add functionality to GitLab.
View project integrations
Prerequisites:
- You must have at least the Maintainer role for the project.
To view the available integrations for your project:
- On the top bar, select Main menu > Projects and find your project.
- On the left sidebar, select Settings > Integrations.
You can also view and manage integration settings across all projects in an instance or group. For a single project, you can choose to inherit the instance or group configuration, or provide custom settings.
NOTE: Instance and group-based integration management replaces service templates, which were removed in GitLab 14.0.
Manage SSL verification
By default, the SSL certificate for outgoing HTTP requests is verified based on an internal list of Certificate Authorities. This means the certificate cannot be self-signed.
You can turn off SSL verification in the configuration settings for webhooks and some integrations.
Available integrations
You can configure the following integrations.
| Integration | Description | Integration hooks |
|---|---|---|
| Asana | Add commit messages as comments to Asana tasks. | {dotted-circle} No |
| Assembla | Manage projects. | {dotted-circle} No |
| Atlassian Bamboo CI | Run CI/CD pipelines with Atlassian Bamboo. | {check-circle} Yes |
| Bugzilla | Use Bugzilla as the issue tracker. | {dotted-circle} No |
| Buildkite | Run CI/CD pipelines with Buildkite. | {check-circle} Yes |
| Campfire | Connect to chat. | {dotted-circle} No |
| Confluence Workspace | Use Confluence Cloud Workspace as an internal wiki. | {dotted-circle} No |
| Custom issue tracker | Use a custom issue tracker. | {dotted-circle} No |
| Datadog | Trace your GitLab pipelines with Datadog. | {check-circle} Yes |
| Discord Notifications | Send notifications about project events to a Discord channel. | {dotted-circle} No |
| Drone CI | Run CI/CD pipelines with Drone. | {check-circle} Yes |
| Emails on push | Send commits and diff of each push by email. | {dotted-circle} No |
| EWM | Use IBM Engineering Workflow Management as the issue tracker. | {dotted-circle} No |
| External wiki | Link an external wiki. | {dotted-circle} No |
| GitHub | Obtain statuses for commits and pull requests. | {dotted-circle} No |
| Google Chat | Send notifications from your GitLab project to a room in Google Chat. | {dotted-circle} No |
| Harbor | Use Harbor as the container registry. | {dotted-circle} No |
| irker (IRC gateway) | Send IRC messages. | {dotted-circle} No |
| Jenkins | Run CI/CD pipelines with Jenkins. | {check-circle} Yes |
| JetBrains TeamCity CI | Run CI/CD pipelines with TeamCity. | {check-circle} Yes |
| Jira | Use Jira as the issue tracker. | {dotted-circle} No |
| Mattermost notifications | Send notifications about project events to Mattermost channels. | {dotted-circle} No |
| Mattermost slash commands | Perform common tasks with slash commands. | {dotted-circle} No |
| Microsoft Teams notifications | Receive event notifications. | {dotted-circle} No |
| Packagist | Keep your PHP dependencies updated on Packagist. | {check-circle} Yes |
| Pipelines emails | Send the pipeline status to a list of recipients by email. | {dotted-circle} No |
| Pivotal Tracker | Add commit messages as comments to Pivotal Tracker stories. | {dotted-circle} No |
| Prometheus | Monitor application metrics. | {dotted-circle} No |
| Pumble | Send event notifications to a Pumble channel. | {dotted-circle} No |
| Pushover | Get real-time notifications on your device. | {dotted-circle} No |
| Redmine | Use Redmine as the issue tracker. | {dotted-circle} No |
| Shimo Workspace | Use Shimo instead of the GitLab Wiki. | {dotted-circle} No |
| GitLab for Slack app | Use Slack's official GitLab application. | {dotted-circle} No |
| Slack notifications | Send notifications about project events to Slack. | {dotted-circle} No |
| Slack slash commands | Enable slash commands in a workspace. | {dotted-circle} No |
| Squash TM | Update Squash TM requirements when GitLab issues are modified. | {check-circle} Yes |
| Unify Circuit | Send notifications about project events to Unify Circuit. | {dotted-circle} No |
| Webex Teams | Receive events notifications. | {dotted-circle} No |
| YouTrack | Use YouTrack as the issue tracker. | {dotted-circle} No |
| ZenTao | Use ZenTao as the issue tracker. | {dotted-circle} No |
Project webhooks
You can configure a project webhook to listen for specific events like pushes, issues, or merge requests. When the webhook is triggered, GitLab sends a POST request with data to a specified webhook URL.
For more information, see Webhooks.
Push hooks limit
Introduced in GitLab 12.4.
If a single push includes changes to more than three branches or tags, integrations
supported by push_hooks and tag_push_hooks events aren't executed.
You can change the number of supported branches or tags by changing the
push_event_hooks_limit application setting.
Contribute to integrations
If you're interested in developing a new native integration for GitLab, see:
Troubleshooting
Some integrations use hooks to integrate with external applications. To confirm which ones use integration hooks, see the available integrations. For more information, see webhook troubleshooting.
Test Failed. Save Anyway error
Some integrations fail with an error Test Failed. Save Anyway when you set them
up on uninitialized repositories. This error occurs because the integration uses
push data to build the test payload, and there are no push events in the project.
To resolve this error, initialize the repository by pushing a test file to the project and set up the integration again.