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.
- On the My Services dashboard, clickContent Management.
- UnderContent, click the name of the content package to capture.
- Click the name of the content package to test.
- Click the three vertical dots to the right of the version to check in, and selectCheck In.
- Enter thePipeline Name, and then select a content endpoint from the drop-down list.
- TheREPOSITORYandBRANCHincludes the default values.
- For aVMware Aria Automation Orchestratorpackage merge, perform the following steps.
- Select theInclude all dependenciesoption to include all dependencies associated with the content package in the check-in.
- Select theMerge with delete contentoption to delete content files from source control that are removed from source endpoint forVMware Aria Automation Orchestrator.
- Add a descriptive comment in theCommentfield, and clickCHECK 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 , 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 customVMware Aria Automation Orchestratorpackage from an endpoint to an uber package version inVMware Aria Suite Lifecycle.
- The ability to merge a customVMware Aria Automation Orchestratorpackage directly to an uber package in GitLab.
- You can release a subset of contents from anVMware Aria Automation Orchestratorpackage 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 aVMware Aria Automationcontent check in with dependency and enabled the option to merge the dependentVMware Aria Automation Orchestratorpackage to an uber package directly on GitLab. When you check-out the sameVMware Aria Automationcontent with dependency from a source control.
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
.