You can check-in the previously captured content to a source control endpoint.

Prerequisites

Verify that you have added a source control endpoint to vRealize Suite Lifecycle Manager. See Source Control with vRealize Suite Lifecycle Manager Content Lifecycle Management for source control requirements.

Procedure

  1. Under Content Management, click Content.
  2. Click the name of the content package to test.
  3. Click the three vertical dots to the right of the version to check in, and select Checkin.
  4. Select a content endpoint to check the content package in to.
  5. Select Include all dependencies to include all dependencies associated with the content package in the check-in.
  6. Add a descriptive comment in the Comment field, and click CHECK IN.
    Note: Adding a check-in comment is mandatory.
    When checking in a vRO package, there is an optional capability to merge with an existing vRO 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 vRO package in which it needs to be merged. With vRealize Suite Lifecycle Manager 2.1 patch, you have the following new features added when you check in an Orchestrator package:

    • You can merge a custom orchestrator-package from an endpoint to an uber package version in LCM.

    • The ability to merge a custom Orchestrator-package directly to an uber package in GitLab.

    • You can release a subset of contents from an Orchestrator-package while deploying to an endpoint.

    • As part of the dependency management, you can remove dependency from a content version.

    For a vRealize Automation content check-out, 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 vRealize Automation content check in with dependency and enabled the option to merge the dependent Orchestrator-Package to an uber package directly on GitLab. When you check-out the same Automation content with dependency from a source control, you can perform the following operation to resolve the dependency hierarchy correctly.
    • Check-out the uber package and deploy to the endpoint.
    • In vRealize Suite Lifecycle Manager 2.1, when you perform a checkout operation on an automation content from git lab (checked-in using 2.0 instance), the only way to get the content with dependency is either by creating a dependency manifest file directly on the git lab or perform another capture and check-in. You can perform check-out without dependency. When you try to deploy 2.0 content, check-in and deploy in 2.1, you encounter an error. This is because, you cannot check-out the content with dependancies in Lifecycle Manager 2.0.
    • Check-out the vRealize Automation content with dependency and deploy to the endpoint.

Results

If a code review is disabled on the source control branch, the content is auto merged.

What to do next

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 vRealize Suite Lifecycle Manager.

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.