- Accessing integrations
- Integrations listing
- Push hooks limit
- Project integration management
- Troubleshooting integrations
- Contributing to integrations
Integrations allow you to integrate GitLab with other applications. They are a bit like plugins in that they allow a lot of freedom in adding functionality to GitLab.
To find the available integrations for your project:
- On the top bar, select Menu > Projects and find your project.
- On the left sidebar, select Settings > Integrations.
There are more than 20 integrations to integrate with. Select the one that you want to configure.
Click on the service links to see further configuration instructions and details.
|Asana||Add commit messages as comments to Asana tasks.||No|
|Atlassian Bamboo CI||Run CI/CD pipelines with Atlassian Bamboo.||Yes|
|Bugzilla||Use Bugzilla as the issue tracker.||No|
|Buildkite||Run CI/CD pipelines with Buildkite.||Yes|
|Campfire||Connect to chat.||No|
|Confluence Workspace||Replace the link to the internal wiki with a link to a Confluence Cloud Workspace.||No|
|Custom issue tracker||Use a custom issue tracker.||No|
|Datadog||Trace your GitLab pipelines with Datadog.||Yes|
|Discord Notifications||Send notifications about project events to a Discord channel.||No|
|Drone CI||Run CI/CD pipelines with Drone.||Yes|
|Emails on push||Send commits and diff of each push by email.||No|
|EWM||Use IBM Engineering Workflow Management as the issue tracker.||No|
|External wiki||Link an external wiki.||No|
|Flowdock||Send notifications from GitLab to Flowdock flows.||No|
|GitHub||Obtain statuses for commits and pull requests.||No|
|Google Chat||Send notifications from your GitLab project to a room in Google Chat.||No|
|irker (IRC gateway)||Send IRC messages.||No|
|Jenkins||Run CI/CD pipelines with Jenkins.||Yes|
|JetBrains TeamCity CI||Run CI/CD pipelines with TeamCity.||Yes|
|Jira||Use Jira as the issue tracker.||No|
|Mattermost notifications||Send notifications about project events to Mattermost channels.||No|
|Mattermost slash commands||Perform common tasks with slash commands.||No|
|Microsoft Teams notifications||Receive event notifications.||No|
|Packagist||Keep your PHP dependencies updated on Packagist.||Yes|
|Pipelines emails||Send the pipeline status to a list of recipients by email.||No|
|Pivotal Tracker||Add commit messages as comments to Pivotal Tracker stories.||No|
|Prometheus||Monitor application metrics.||No|
|Pushover||Get real-time notifications on your device.||No|
|Redmine||Use Redmine as the issue tracker.||No|
|Slack application||Use Slack’s official GitLab application.||No|
|Slack notifications||Send notifications about project events to Slack.||No|
|Slack slash commands||Enable slash commands in workspace.||No|
|Unify Circuit||Send notifications about project events to Unify Circuit.||No|
|Webex Teams||Receive events notifications.||No|
|YouTrack||Use YouTrack as the issue tracker.||No|
Introduced in GitLab 12.4.
If a single push includes changes to more than three branches or tags, services
tag_push_hooks events aren’t executed.
The number of branches or tags supported can be changed via
push_event_hooks_limit application setting.
Project integration management lets you control integration settings across all projects of an instance. On the project level, administrators you can choose whether to inherit the instance configuration or provide custom settings.
Read more about Project integration management.
Some integrations use service hooks for integration with external applications. To confirm which ones use service hooks, see the integrations listing above. Learn more about troubleshooting service hooks.
Some integrations fail with an error
Test Failed. Save Anyway when you attempt to set them up on
uninitialized repositories. Some integrations use push data to build the test payload,
and this error occurs when no push events exist in the project yet.
To resolve this error, initialize the repository by pushing a test file to the project and set up the integration again.
Because GitLab is open source we can ship with the code and tests for all plugins. This allows the community to keep the plugins up to date so that they always work in newer GitLab versions.
For an overview of what integrations are available, please see the integrations source directory.
Contributions are welcome!