Connect Gitlab to Rovo
Before you begin
Rovo supports all of GitLab’s SaaS plans (Free, Premium, Ultimate). GitLab Self Managed and GitLab Dedicated are not currently supported.
Only repositories are available to Rovo.
You must be a Maintainer or Owner for any organizational groups to connect to Rovo.
Rovo will index repositories from any group where the connecting account holds a Maintainer or Owner role. Due to the way Gitlab permissions work, this may include content outside your primary organisation (open source groups, client organizations etc). We strongly recommend reviewing your roles in each of your GitLab groups before connecting your account.
Rovo will always respect permissions. Users will only ever see repositories that they already have access to.
Connecting to GitLab
To get to the setup screen for GitLab:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Settings > Rovo.
Under Activated sites, next to the site you want to connect, select More actions () and select Add connector.
Select GitLab and press Next.
Next, to configure GitLab:
Enter a name for your GitLab connection.
Review the disclaimer.
Select Authorize GitLab.
A new tab will open to step you through GitLab authorization. Review and accept the permissions to connect. Select Authorize Atlassian Rovo.
Next steps
After you’ve finished connecting GitLab:
Pages will start to show in Search incrementally over the next few hours.
Your team members will see GitLab show up as a filter option in Search. If they haven’t connected to GitLab from their Atlassian account, they may be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see content that they already have access to.
Depending on the number of repositories in GitLab, it may take some time for all your repositories to be indexed and appear in Search.
Was this helpful?