You can define a content release and manage source control access while you configure extensibility of your content release.

Pipeline Stubs

The pipeline stubs display the status of each action whenever a content is captured. The content pipeline has the following status types whenever a content is run.

  • Pre-Capture

  • Post-Capture

  • Pre-Test

  • Post-Test

  • Pre-Release

  • Post-Release

Source Control Access

To add a source control endpoint, provide a server for that source control from GitLab. For more information, see Add a Source Control Server Endpoint.

Note:

You can add multiple server names for a source control server endpoint and only GitLab source control is supported for this version.

vSphere Template Repository

Starting with vRealize Suite Lifecycle Manager 1.3 and later, you can capture content from vSphere vCenter Server, the vSphere Template Repository is a Content Library within a designated vCenter instance that will store all the templates that are captured in which they can be managed from LCM. A best practice is to have this vCenter instance close to where the templates would typically be captured, that is a development vCenter for template authoring. You can go back to Endpoints and select vCenter to add as your endpoint. For more information, see Add a vCenter Server Content Endpoint. The model for the Content Library Configuration is the following:

  1. Create the Content Library (Publisher): The vSphere Template Repository points to a Content Library that is set up for publishing. For more details on how to setup a publisher Content Library, see vCenter Documentation:

  2. Create Content Library Subscribers: Each vCenter server that will have templates from LCM requires a Content Library to be configured which will Subscribe to the Published Library configured in Step 1. The following settings are required :

Setting

Description

Automatic Synchronization

You can enable this setting for automatic synchronization of the template metadata.

Subscription URL

This URL contains details about the publishers lib.json file. This will be available when you create a publisher in Step 1.

Authentication Disabled

Disabled

Library content

  • Download all library immediately - If you don't select this option then vCenter will download ALL virtual machine templates.

  • Download library content only when needed - Only the metadata is downloaded (not the disks). vRSLCM instructs on demand and as requested to download the associated disks

Developer Restrictions

Content tags are useful for a variety of reasons, to locate content within the UI, that is when you find all content with "BugFix-Task-1" tag or can be used for custom business logic during the release pipeline.

An example of this may be custom business logic implemented by a release manager - Don't Deploy Content to Endpoint B unless the Content has been deployed to Endpoint B, first this requires a custom pipeline/workflow to be implemented. If this rule is to be bypassed, for example, for Release Mangers to push Content straight to Endpoint B then a tag could be applied to the content. This tag should only be added by a Release Manager and not a Developer.