Getting Started
LinearB Slack Application Updates
Frequently Asked Questions
Connect to Jira and set the board for your team
Set up your initial team
LinearB Trial Setup
Daily Workflows
Onboarding Help
Onboarding Troubleshoot
Github server (on-prem) connection guide
BitBucket server (on-prem) connection guide
GitLab server (on-prem) connection guide
Connect Github with a personal access token
Set up release detection method
Jira (cloud) connection guide
Jira server (on-prem) connection guide
How to create a Clubhouse API token
Troubleshoot - Can't find my repositories after authorizing LinearB in Github
Connect LinearB to your Project Management Tool
How to
How to - Create and manage teams
How to - Connect and manage slack notifications
How to - Invite new users
How to - Work with team dashboard
How to - Handle High Risk Work
How to - Handle Material Pull Request Merged w/o Review or Basic Review
How to - Handle Hanging Review Requests and Long Reviews
How to - Manage and Customize Notifications
How to - Merge accounts
How to - Use Slack commands
How to - Set Jira board per team
Tutorials
What is Cycle Time for Software Developers?
Utilizing Teams
Detecting high risk work
Lightning PRs action filter
Long Living PR Action Filter
Using the App
Main Metrics
Cycle Time
Work Breakdown
Investment Profile
Time Distribution
Code Change Rate
Deployment Frequency
PR Open Rate
Review Depth
Time to Merge
Velocity
Throughput Metrics
Pull Request Size
Branches Filters
WIP (Work In Progress)
High Risk
Branch State
Done in Iteration
High Rework
Point in History
Carryover from Iteration
Pull Request Filters
Updated in Iteration
Lightning Pull Requests
Review Request Hanging
Long Living Pull Requests
Pull Request State
Merged Without Review
Merged in Iteration
High Interaction Pull Requests
Pulse View
Understanding Pulse View
Draft Pull Requests
Pulse Alerts
Pulse naming conventions - Jira
Pulse naming conventions - Clubhouse
Notification Types
Ineffective code contribution
Projects active contributors
Work Breakdown Terms
Understanding Code Changes
Quality Code Metrics Explained
Release Notes
- All Categories
- Onboarding Help
- GitLab server (on-prem) connection guide
GitLab server (on-prem) connection guide
Updated
by Boaz Dremer
GitLab server (on-prem) connection guide
In order to connect your LinearB application to GitLab server (on-prem) you will need to do the following:
Select GitLab Server as your Git provider
In the source control selection dialog select GitLab Server.

IP Whitelisting
If your GitLab Server instance is available from the public internet, you can skip this step.
In order for LinearB to be able to access your private network, you will need to add LinearB’s public IP as a whitelisted source in your network firewall.
LinearB’s public IP: 52.15.80.85
In case that your network is behind a VPN, it is standard to have some reverse proxy that allows LinearB specific access to GitLab Server.
Insert your GitLab server URL
Once you whitelist LinearB IP in your network insert your GitLab's server URL. LinearB will automatically check connectivity to your GitLab server. Once the connection is established you will be able to move to the next stage

Create a Personal Access Token
- Log in to GitLab Server.
- In the upper-right corner, click your avatar and select Settings.

- On the User Settings menu, select Access Tokens.

- Choose a name and optional expiry date for the token.
- Select the following access scopes: read_user, api, read_repository.
- Click the Create personal access token button.

Copy the token to a secure file and hit continue.
Important: You will no longer be able to view the value of the token once you hit continue. Make sure you copied it first.

Paste the access token to the text box. LinearB will automatically check the validity of the access token. Once the access token is validated. You will be able to move to the next stage (Repository selection)
