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

Check in content to a source control endpoint

You can check-in the previously captured content to a source control endpoint by using
VMware Aria Suite Lifecycle
.
Verify that you have added a source control endpoint to
VMware Aria Suite Lifecycle
. See Source Control with vRealize Suite Lifecycle Manager Content Lifecycle Management for source control requirements.
We support a single content check-in, with a maximum of 1000 files at a time.
  1. On the My Services dashboard, click
    Content Management
    .
  2. Under
    Content
    , click the name of the content package to capture.
  3. Click the name of the content package to test.
  4. Click the three vertical dots to the right of the version to check in, and select
    Check In
    .
  5. Enter the
    Pipeline Name
    , and then select a content endpoint from the drop-down list.
  6. The
    REPOSITORY
     and
    BRANCH
     includes the default values.
  7. For a
    VMware Aria Automation Orchestrator
     package merge, perform the following steps.
    • Select the
      Include all dependencies
       option to include all dependencies associated with the content package in the check-in.
    • Select the
      Merge with delete content
       option to delete content files from source control that are removed from source endpoint for
      VMware Aria Automation Orchestrator
      .
  8. Add a descriptive comment in the
    Comment
     field, and click
    CHECK IN
    .
Adding a check-in comment is mandatory.
When checking in a
VMware Aria Automation Orchestrator
 package, there is an optional capability to merge with an existing
VMware Aria Automation Orchestrator
 package that exists in the source control. This ensures that all files that are captured are checked into the path of the selected package (ultimately merged). If you do not see the package, then
Select the Source Control Endpoint
Orchestrator-Package type
, refresh the cache and check- in to view the
VMware Aria Automation Orchestrator
 package in which it needs to be merged. You have the following new features added when you check in a
VMware Aria Automation Orchestrator
 package:
  • You can merge a custom
    VMware Aria Automation Orchestrator
     package from an endpoint to an uber package version in
    VMware Aria Suite Lifecycle
    .
  • The ability to merge a custom
    VMware Aria Automation Orchestrator
     package directly to an uber package in GitLab.
  • You can release a subset of contents from an
    VMware Aria Automation Orchestrator
     package while deploying to an endpoint.
  • As part of the dependency management, you can remove dependency from a content version.
For a
VMware Aria Automation
 content check-in, you can merge directly on GitLab. You can check out without dependency or check out with dependency, where you can perform the following:
  • You can remove the package dependency from the latest version. For example, if you have performed a
    VMware Aria Automation
     content check in with dependency and enabled the option to merge the dependent
    VMware Aria Automation Orchestrator
     package to an uber package directly on GitLab. When you check-out the same
    VMware Aria Automation
     content with dependency from a source control.
If a code review is disabled on the source control branch, the content is auto merged.
If a code review is enabled on the source control branch, you or another code reviewer must check the content in to GitLab manually after the code review is complete. After you check the content into GitLab, capture the latest content version from the source control server in
VMware Aria Suite Lifecycle
.
If you are continuing to develop on your content endpoint, capture the latest content version from source control and deploy it to your development content endpoint. This updates the content endpoint so that the content is in sync with the source control and subsequent check-ins are valid.
You can view the check in status in the
Activity Log
.

Content feedback and comments