Sentry’s GitLab integration helps you find and fix bugs faster by using data from your GitLab commits. Additionally, you can streamline your triaging process by creating a GitLab issue directly from Sentry.
In Sentry, navigate to Organization Settings > Integrations.
Within Integrations, find the GitLab icon and click Install.
In the resulting modal, click Add Installation.
In the pop-up window, complete the instructions to create a Sentry app within GitLab. Once you’re finished, click Next.
Fill out the resulting GitLab Configuration form with the following information:
The GitLab URL is the base URL for your GitLab instance. If using gitlab.com, enter https://gitlab.com/.
Find the GitLab Group Path in your group’s GitLab page.
Find the GitLab Application ID and Secret in the Sentry app within GitLab.
Use this information to fill out the GitLab Configuration and click Submit.
In the resulting panel, click Authorize.
In Sentry, return to Organization Settings > Integrations. You’ll see a new instance of GitLab underneath the list of integrations.
Next to your GitLab Instance, click Configure. Note: It’s important to configure to receive the full benefits of commit tracking.
On the resulting page, click Add Repository to select which repositories in which you’d like to begin tracking commits.
Issue tracking allows you to create GitLab issues from within Sentry and link Sentry issues to existing GitLab issues.
Select your issue
Navigate to Linked Issues on the right panel of the issue’s page and click Link GitLab Issue.
You have two options to complete the issue link:
To unlink an issue, click on the X next to its name under Linked Issues.
Commit tracking allows you to hone in on problematic commits. With commit tracking, you can better isolate what might be problematic by leveraging information from releases like tags and metadata.
Once you’ve configured both release and commit tracking, you’ll be able to see more thorough information about a release: who made commits, which issues were newly introduced by this release, and which deploys were impacted.
When you investigate deeper into that commit, you can leverage information from metadata like tags.
Broadly, this lets you isolate problems in order to see which commits might be problematic.
Learn more about release and commit tracking.
Once you are tracking the commits, the ‘suspect commit’ is the commit that likely introduced the error.
One special benefit of using Sentry’s Commit Tracking is the ability to know the suspect commit that likely caused the error, with a suggested plan of action for how to rectify the error. For example, after pinpointing the suspect commit, you can also identify the developer who made the commit and assign them the task of fixing the error.
Here is where you can find info for suspect commit setup.
Resolve via Commit or PR
Once you’ve added a repository (see configuration step 8), you can start resolving issues by including
fixes in your commit messages. You might want to type something in the commit like: “this fixes MyApp-AB12” or “Fixes MyApp-317”. The keyword to include is fixes. You can also resolve issues with pull requests by including
fixes in the title or description. This will automatically resolve the issue in the next release.
may look something like ‘BACKEND-C’ in the image below.
- I’m using GitLab on-premise. Do I need to whitelist Sentry’s IP addresses?
- Yes. You can find our IP ranges here .
- Do you support subgroups?
- Currently, we only support subgroups for users using GitLab 11.6 or higher.
- My repositories are hosted under my user account, not a group account. Can I still use this integration?
- Unfortunately, not. The GitLab integration only works for repositories that are hosted under group accounts.
- Are there pricing restrictions?
- This integration is available for organizations on the Team, Business, or Enterprise plan.
- Who has permission to install this?
- You must have both owner/manager permissions in Sentry and owner permissions in GitLab to successfully install this integration.