Tools Connect: GitLab
- Anand Chauhan
Allstacks collects data about your commits, pull requests, branches, and other related coding activities for a complete view of engineering efforts.
Allstacks service connection to GitLab is established via OAuth or API Token. We recommend using GitLab (OAuth) for connecting to GitLab SaaS while GitLab (Basic) is used for hosted GitLab Self-Managed.
GitLab (Basic)
Before starting, confirm that you are actively signed into GitLab with the account, preferably service account, you wish to connect to Allstacks.
In Allstacks, click on “Add Tool” and select GitLab (Basic) as an option to connect to self-managed hosted GitLab instance.
The GitLab URL should point to the base URL for your GitLab instance.
Create GitLab API token with Reporter permission scope, and connect GitLab to Allstacks using that token.
Reporter permissions access in GitLab as described here: Permissions and roles | GitLab
Now in Allstacks clicking “ADD TOOL” you will direct you to the Allstacks service connection workflow.
On successful connection, you will see a list of resources you can toggle on and off the projects. In the event this list is blank you may need to press “Refresh Resources”.
GitLab (OAuth)
Before starting, confirm that you are actively signed into GitLab with the account you wish to connect to Allstacks.
Verify GitLab permissions for service account:
The service user you create to establish the connection with Allstacks will need Reporter permissions access in GitLab as described here: Permissions and roles | GitLab
Note that selecting “ADD TOOL” will redirect you to GitLab starting the authorization process.
On successful connection, you will see a list of resources you can toggle on and off the organization and repositories respectively. In the event this list is blank you may need to press “Refresh Resources”.