To add a source control server to the system, add a source control server endpoint.

When you disable the file editor option then the bitbucket API (PUT/POST) does not work for an admin or a developer. Either do not include the below property (feature.file.editor) in the property files or if this is included then ensure that the property is set to true.

Location: <base_directory>\Atlassian\ApplicationData\Bitbucket\shared\bitbucket.properties

Properties: feature.file.editor=true

Prerequisites

  • Verify that you have a Bitbucket, GitHub or a GitLab instance that is supported for this version of vRealize Suite Lifecycle Manager. For more information on the supported versions of Bitbucket, GitHub, or GitLab, refer to Content Lifecycle Management.
  • Log in to GitHub, GitLab or Bitbucket, and generate an access token for your user with all scopes enabled. Copy and save this one-time token from GitHub, GitLab or Bitbucket.
  • Log in to GitHub, GitLab or Bitbucket and verify you have group, project and branch created in GitHub, GitLab or Bitbucket before adding it as a source control endpoint.

Procedure

  1. On the My Services Dashboard, click Content Management.
  2. Click Content Settings.
  3. On the Source Control Access tab, click ADD SOURCE CONTROL SERVER.
  4. Select the Source Control Type.
    Note: With vRealize Suite Lifecycle Manager 8.0, you can now select Bitbucket Server or Bitbucket Cloud.
  5. 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 must be specified in <GroupName>/<ProjectName> form. Whenever multiple developers are working on the bit bucket repository then the performance is slow in the bit bucket enterprise version. Therefore, you can use at least 4 vCPU machine of bit bucket.
  6. Click the pencil icon for the source control server.
  7. Enter your GitLab or Bitbucket server access token in the ACCESS KEY text box, and click SUBMIT.
    1. For a GitHub instance, you can either select to enter the credential of the Github instance by providing the user name and password or enter the access token.
    2. Click SUBMIT.
    An access token is a unique identity for a user to perform check-in or check-out to track the GitLab or GitHub API. To create an access token for GitLab or GitHub, access the GitLab or GitHub Server URL. For example, gitlab.example.com or github.com. For Bitbucket Server and Cloud, browse to bitbucket.org and navigate to App Passwords to create a password with full permissions.