You can import a release pipeline model to avoid recreating a release pipeline.

You can import pipelines that were previously exported from 2.3 and 2.2 versions of vRealize Code Stream.

If the release pipeline is using a configured endpoint, configure the endpoint on the appliance before you import the release pipeline. If an endpoint is not configured on the appliance, an error message occurs.

To use the vRealize Code Stream user interface to import pipelines, see Importing Pipelines.

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>

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>