VMware Aria Suite Lifecycle 8.16

8.18 8.16 8.14 8.12
Português (Brasil) 简体中文 Deutsch Español Français Italiano 日本語 한국어 Nederlands 繁體中文 English

Add a source control server endpoint in
VMware Aria Suite Lifecycle

To add a source control server to the system, use the Content Management service in
VMware Aria Suite Lifecycle
 to add a source control server endpoint.
  • Verify that you have access to a Bitbucket, GitHub, or GitLab instance that is supported for this version of
    VMware Aria Suite Lifecycle
    . For more information on the supported versions of Bitbucket, GitHub, and GitLab, see Working with Content Management in VMware Aria Suite Lifecycle.
  • Log in to GitHub, GitLab, or Bitbucket, and generate an access token for your user that supports all scopes. Copy and save this one-time token.
  • Log in to GitHub, GitLab, or Bitbucket and verify the existing group, project, and branch before adding the instance as a source control endpoint.
When you deactivate the file editor option, the Bitbucket API (PUT/POST) is not accessible to an administrator or developer. Do not include the
feature.file.editor
 property in the property file or set the property to
true
.
Location:
base_directory
\Atlassian\ApplicationData\Bitbucket\shared\bitbucket.properties
Properties:
feature.file.editor=true
Use the following procedure to add a source control server endpoint.
  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
    .
  5. Enter the IP address or fully qualified domain name of the server and click
    SUBMIT
    .
    VMware Aria Suite Lifecycle
     uses
    https
     format for any source control APIs by default. If you have not activated
    https
     on the GitLab instance, then specify
    http://
    ip address
    :
    port
     for the source control server on the content settings page to change the format. When you create a source control endpoint, the repository must be specified using a
    GroupName
    /
    ProjectName
     format. Use at least a 4 vCPU Bitbucket machine for optimal performance.
  6. Click the
    Edit
     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, enter the credentials for the user name and password or 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. Create an access token for GitLab or GitHub by specifying 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.

Content feedback and comments