After a content is checked in to a source control endpoint, you can check out the content and deploy it to a content endpoint. When the content is checked out from Source Control, the content is marked with the Git Hash Code for reference.

Prerequisites

Verify that the content has been checked in to the source control endpoint. See Check in Content to a Source Control Endpoint.

Procedure

  1. Under Content Management, click Content.
  2. Click ADD CONTENT.
    Note:

    You can check out the content inline as well.

  3. Choose whether to test or deploy the content package in addition to capturing it, and click PROCEED.
  4. Enter the capture details for the content package.
    1. From the Select Capture Endpoint drop-down menu, select the source control endpoint to capture content from.
    2. Select Get the latest content to retrieve the latest content dependencies rather than the dependencies the content was initially captured with.
    3. Select the content type and content to capture.
    4. Select Include all dependencies to capture any dependencies associated with the content.

      Dependencies are stored in vRealize Suite Lifecycle Manager, not the source control endpoint.

    5. If the content is ready for production, select Mark this version as production ready.
    6. Enter a description for this content version in the Comments field.
    7. Click Next.
  5. Enter test details for the content endpoint.

    This option appears only if you selected to test the content package.

    1. Select one or more content endpoints to specify the environments to run tests on.
    2. Select Deploy Content to deploy the content in the endpoint before running tests.
    3. Select Stop test deployment on first failure to stop the test deployment as soon as it encounters an error.
    4. Select Run unit tests to run available unit tests on the content.
    5. Select Stop unit tests on first failure to stop testing if any unit test fails.
    6. Select a server to run unit tests on from the Select a Unit Test Server drop-down menu.

      You must have a vRealize Orchestrator test package imported to use a unit test server.

    7. Click Next.
  6. Enter deployment details for the content package.

    This option appears only if you chose to test the content package.

    1. Select one or more content endpoints from the Select Release Endpoints drop-down menu to specify the production environments where the system releases the content.
    2. Select Stop release deployment on first failure to stop deployment as soon as the system encounters a failure.
    3. Enter a comment that explains why the content is being released in the Release Comment field as writing comments are mandatory.
  7. Click SUBMIT.

Results

vRealize Suite Lifecycle Manager captures the content from the source control endpoint and creates a new version of the content in the content catalog. This version is marked SourceControl Enabled, which tells vRealize Suite Lifecycle Manager the state of the content when deploying to a content endpoint so the content is checked in against the right point in time.

What to do next

If you are using source control and have multiple capture content endpoints, only deploy content from the content catalog is marked SourceControl Enabled. This communicates the state of the content when deploying to a content endpoint so the content is checked in against the right point in time.