Connect gitStream Using a GitLab Integration
To connect gitStream to your GitLab integration in LinearB, there few steps you need to do: Connect gitStream. Go to Settings -> Git -> click the Connect gitStream button next to your Git integration…
Updated
by Betsy Rogers
To connect gitStream to your GitLab integration in LinearB, there few steps you need to do:
Connect gitStream
- Go to Settings -> Git -> click the Connect gitStream button next to your Git integration
- You can use your existing GitLab integration or create a new one.
When using gitStream with GitLab, all automations will be triggered using the GitLab account name that was used to connect with LinearB. It is recommended to review the account name connected, and consider changing it to a service account with a more meaningful identifier such as gitStream-cm to ensure clarity and proper identification of the automated actions.
Create a cm repo with your CI script
- Create a cm project (repository) in your GitLab group. It should be created in the same group or a parent group of the target repositories.
- Create a .gitlab-ci.yml file in your new cm repository's default branch (usually master or main) and add the following configuration found here: https://docs.gitstream.cm/downloads/gitlab-ci.yml
Create your first automation!
Set up gitStream automation rules for a single repo or your entire GitLab organization. Choose the tab below for your preferred instructions.
For both single and org level configurations, the code content should be viewed from here: https://docs.gitstream.cm/downloads/gitstream.cm
- Single Repository
- Create a .cm/gitstream.cm rules file in your repository's default branch (usually master or main). This file will contain a YAML configuration that determines the workflows that run on the repo, and you can name it anything you want as long as it ends in .cm
- Org Level
- Create a gitstream.cm rules file in the root directory of your cm repository's default branch (usually master or main). This file will contain a YAML configuration that determines the workflows that run on your organization's repos. You can name it anything you want as long as it ends in .cm
- Connect the cm repo.
- Connect the other repos
- Select all or specific repos you like gitStream to cover
How did we do?