Automated MTAR Deployments

Release Pipeline

Release Pipelines enable you to orchestrate deployments into SAP environments with right approvals in place. It can be created with one or more stages. Each stage will correspond to automated deployment of mtar application to SAP BTP subaccount with a sequence of activities such as tasks related to approvals, manual changes, deployments, callouts and tests execution

Note: You can create a multi-stage pipeline for continuous deployment across various environments one after the other towards continuous delivery of application all through Dev - QA - Staging - Production.

Creating a Release Pipeline

Creating a Release Pipeline is a guided six-step process, designed to help you define and configure all necessary stages and parameters for end-to-end deployment automation.

Step1	Enter a name in Release Pipeline Name
Step2	Choose Pipeline Type – SAP BTP or SAP HANA XSA (MTAR) from the drop down
Step3	The dropdown contains all the build pipelines of type MTAR. Choose the build pipeline whose mtar artifact must be deployed.
Step4	Click Add Stages, add the stages. Add various types of pre, post and deployment tasks on need basis.
Step5	Choose to schedule the pipeline execution or run manually
Step6	Specify the email ids to receive notifications about release pipeline execution status.

To create a release pipeline:

1. In Release, go to Release Pipelines.

2. Click Create New Release Pipeline.

1. Release Pipeline Name: Give a name for the release pipeline.

a) Pipeline Type: For SAP Cloud (MTAR) project, the Pipeline Type appears SAP BTP (MTAR) by default and is read-only.

b) For SAP HANA XSA (MTAR) project, the Pipeline Type appears SAP HANA XSA (MTAR) by default and is read-only.

1. Artifact Source: The dropdown contains all the build pipelines of type MTAR. Choose the build pipeline with the necessary artifacts to be deployed in the environment.

1. Add Stages: Click Add Stage and enter the stage name say for e.g., UAT or QA where the deployment has to be carried out and click OK.

The newly added stage appears as follows:

Note: To remove any stage, click Remove Stage button.

Tasks: Click Add to enter any tasks that are to be performed as desired. (Deployment, Approvals, Manual Task, Callout, Test Execution and User Story Status Update)

Note: Deployment Task varies for different project types.

Deployment Task – All the details pertaining to the deployment of the artifact is specified in deployment task.The following screen is displayed on adding a deployment task.

Cloud Transport Management

• SAP Cloud Transport Management service allows you to manage the transport of development artifacts and application-specific content between different SAP BTP accounts.

Note: Further information on Cloud Transport Management System can be found at https://help.sap.com/docs/TRANSPORT_MANAGEMENT_SERVICE/7f7160ec0d8546c6b3eab72fb5ad6fd8/5fef9d6b1cb047b2b18d9eb57aa15352.html

• Select the option Upload Artifact to Cloud Transport Management if the artifact has to be uploaded to any other BTP environment.

The following screen is displayed.

Fill in the required details:

Select Environment	Select an environment from the available list of registered SAP BTP environments where the deployment has to take place.
Service Instance	Select the Service Instance from the available service instances listed in the dropdown.
Service Key	Select the Service Key from the available service keys listed in the dropdown.
Node Name	Enter a node name added in the Cloud Transport Management System corresponding to the environment to which the artifact is to be uploaded.

1. Trigger: You can trigger a Release Pipeline either Manually or on Successful Build it to get triggered automatically once its reference build pipeline gets executed successfully.

1. Notification Emails: You can specify an email distribution list separated by comma who you want to notify the result of the Release Pipeline Execution – either Success or Failure.

Note: If the Release Pipeline fails, the logs are also attached in the notification email. By default, the user who creates the Release Pipeline is notified and specifying the distribution list is optional.

On clicking Save, the release pipeline gets created and is shown in the Release Pipelines screen.

Multi-Stage Release Pipeline

Any number of stages can be added while creating a release pipeline. An existing release pipeline can also be edited to include various stages. This is required when we want the deployments to take place in multiple environments one after the other continuously which is a part of Continuous Delivery. For each stage, the tasks are to be added separately. This corresponds to the tasks that are to be performed in that particular environment for the deployment to take place and the required actions that are to be taken.

Running a Release Pipeline

Once a release pipeline is created, you can run multiple iterations to deploy MTAR artifacts.

To run a release pipeline:

1. Once you create a release package, go to Release, and click Release Pipeline.

2. Choose the required release pipeline to be run and click Run.

3. A pop-up appears. Enter a Cycle Name and Select build from the drop down.

4. Click Trigger Pipeline. A message is displayed, about successful creation of a release pipeline. Click OK. The following screen is displayed:

5. Click Refresh. Click on the required build to view a list of the triggered cycle.

1. Click on the required cycle to view its details.

1. Click Logs¸ to view the logs of this cycle. You can even download the logs by clicking the Download Dmol Log link.

• Click Errors, to view the errors that resulted in the deployment failure.

To view more error details, click View Details.

For a multi-stage Release Pipeline, the execution details of a test cycle in each environment will be shown one after the other in the order of their addition while creating the release pipeline.

Click Deployment Changes to know which user story is associated with a Release Pipeline and which artifacts are a part of it.

Editing a Release Pipeline

Go to the required pipeline in Release Pipeline page and click Edit to edit the pipeline.