To add a source control server to the system, add a source control server endpoint.
Verify that you have a GitLab instance (GitLab Community Edition/Enterprise Editions version 10.5.6+) and is supported for this version of vRealize Suite Lifecycle Manager.
Log in to GitLab and generate an access token for your user with all scopes enabled. Copy and save this one-time token from GitLab.
Log in to GitLab and verify you have group, project and branch created in GitLab before adding it as a source control endpoint.
- Under Content Management, click Content Settings.
- On the Source Control Access tab, click ADD SOURCE CONTROL SERVER.
- Select the Source Control Type.
With Lifecycle Manager 2.1, you can now select Bitbucket Server or Bitbucket Cloud.
- Enter the IP address or fully qualified domain name of the server, and click SUBMIT.
vRealize Suite Lifecycle Manager uses https scheme for any Source Control APIs by default. If you have not enabled https on the GitLab instance, then specify http://<ip address>:<port> in the source control server under the content settings page to change the scheme. When you create source control endpoint, the repository needs to be specified in <GroupName>/<ProjectName> form. Whenever multiple developers are working on the bitbucket repository then the performance is slow in the bitbucket enterprise version. Therefore, you can use at least 4vCPU machine of bitbucket.
- Click the pencil icon for the source control server.
- Enter your GitLab access token in the ACCESS KEY field, and click SUBMIT.
An access token is a unique identity for a user to perform check-in or check-out to track the GitLab API. To create a access token for Gitlab, access the gitlab.eng.vmware.com and create a token name. For Bitbucket Server and Cloud, browse to bitbucket.org.com and navigate to App Passwords to create a password with full permissions.