A source control endpoint represents a project (repository) and a source control server.
You can have any number of source control repositories and branches added to vRealize Suite Lifecycle Manager. Adding a source control branch allows you to check in and check out SDDC content.
Verify that a vRealize Suite Lifecycle Manager administrator has added a system source control server under Content Settings.
Verify that a developer has entered the GitLab access token to the source control server so that they can check-in and check-out content.
- Under Content Management, click Endpoints.
- Click NEW ENDPOINT.
- Select Source Control.
- Select the configured Bitbucket server, cloud, or Gitlab.
- Enter the information for the Source Control content endpoint.
- In the Name field, enter a unique name for the endpoint.
- Enter a Tag name.
- Enter the Branch and Repository Name to use for the content endpoint in the following format: For GitLab, enter
group_name/repository_name, Bitbucket server, enter
project_name/repository_nameand for Bitbucket cloud, enter
In bitbucket cloud, you can only create a repository and use the repository name. The source control endpoint with a repository needs to be initialized with any file. Gitlab and bitbucket cloud already have a provision to add the file but the bit bucket server does not. With Lifecycle Manager 2.1, cluster and elastic search instance for multi developer story is not supported for bitbucket server.
- Click Test Connection and click Next.
- Select the appropriate policies for this content endpoint, and click Next.
Enable code review
Allows a manual review between developers. vRealize Suite Lifecycle Manager content lifecycle management creates a branch with the changes that require a code review. A code reviewer can accept or reject the merge request into the branch.
- Verify that the content endpoint details are correct, and click Submit.