GitLab integration with nested groups

#1

We nest groups for our clients under our main group. For instance, a client repo would live, for us, at https://gitlab.com/my-company/client-company/client-project.

When setting up the GitLab integration, can I put https://gitlab.com/my-company as the Group Path and link to issues in the https://gitlab.com/my-company/client-company/client-project repo? In other words, should Sentry recursively search subgroups when I go to add repositories? Because, right now, I’m getting no results:

0 Likes

#2

we organizse the same way: gitlab-url/org/team/repo. It’s not clear to me what to add in Sentry’s integration setting.

1 Like

#3

I think I figured out that we need to add all teams that want Sentry integration for their repos - the Gitlab integration supports multiple integration “instances” so it’s not a huge problem (aside from it being a bit of a hassle)

0 Likes