1
Create a GitLab Repository
Create a new GitLab private repository using one of these options:
- Create a new repository
- Clone from the Honeydew quick-start example.
2
Configure allowed IP addresses
If you are restricting access to your GitLab group using IP addresses allow list,
add the IP addresses displayed in the GitLab connection screen in Honeydew App settings page
to the restricted IP addresses list in your GitLab group settings.
For the Honeydew Cloud deployment, the following IP addresses are used:
34.86.209.9034.145.147.92
3
Set up Honeydew
Please reach out to support@honeydew.ai and send the full repository name -
org-name/repository-name (e.g. honeydew-ai/honeydew-quickstart).4
Create a GitLab Token
Create a new GitLab token for Honeydew integration:
- In GitLab, under the project you have created for Honeydew, go to Settings -> Access tokens
- Create a new project token:
- Select
Maintaineras the role - Set the following permissions:
apiread_userread_repositorywrite_repository
- Set a far-enough expiration date
- Name the token (e.g.
Honeydew)
- Select
5
Configure the token in Honeydew
In the Honeydew application, go to Settings -> GitLab and configure the token.
To validate semantic-layer changes in your CI/CD pipeline, see the
CI/CD Overview.
Clean up merged branches
Honeydew creates a Merge Request when you publish changes, but does not delete the branch when that Merge Request is merged in GitLab. Enable source branch deletion by default so merged branches do not accumulate in the Honeydew branch list:- In your project, go to Settings -> Merge requests
- Select Enable “Delete source branch” option by default
- Select Save changes
This sets the default for new Merge Requests. Whoever merges can still clear the
Delete source branch checkbox, which leaves the branch in place.The branch is deleted by the user who merges the Merge Request, so that user needs permission
to delete the branch — otherwise the merge succeeds but the branch is not deleted.