You can import a release pipeline model between vRealize Code Stream 1.1 appliances to avoid recreating a release pipeline.

When you use the REST API to upgrade from vRealize Code Stream 1.0 to 1.1, the release pipeline models are migrated to the latest release version.

If the release pipeline is using configured endpoint, configured them on the appliance before you import the release pipeline. If an endpoint is not configured on the appliance, you receive an error message.

HTTP Method

POST

URI Syntax

/release-management-service/api/release-pipelines?action=import&overwrite=false

The overwrite value is set to false by default and is optional. When the overwrite value is set to true, the imported release pipeline model overwrites the existing pipeline with the same name.

Response

The imported release pipeline model can be in the XML or JSON format depending on whether the HTTP Content-Type header is set to application/json or application/xml.

The imported pipeline is always in the draft state.

<release-pipeline-import-response>
   <id>da6019bf-eee2-483d-87b3-2d7752289dda</id>
   <status>rp01 import successful</status>
<release-pipeline-import-response>

Missing Endpoint Response

The endpoint is not configured for the imported release pipeline model.

<errors>
    <error code="18142">
        <message>Importing Release pipeline failed.</message>
        <systemMessage>Instance Jenkins_Sample of plugin RPTestJenkins not found. Please create the plugin instance in the associated vCO</systemMessage>
    </error>
</errors>

Existing Release Pipeline Name Response

The imported release pipeline model name exists.

<errors>
    <error code="18142">
        <message>Importing Release pipeline failed.</message>
        <systemMessage>The pipeline name Sample Pipeline already exists. Please rename the pipeline or use the overwrite option</systemMessage>
    </error>
</errors>