Working with Build Pipelines

This section provides a comprehensive guide for configuring Projects, Build Pipelines, and Release Pipelines in ReleaseOwl for SAP BTP ABAP Cloud environments. By following these steps, teams can ensure controlled, automated, and auditable build and deployment processes within ReleaseOwl.

Create the Project

1. Go to the Administration page of the application.

2. Under the Projects section, locate the Create New Project button.

3. Click on the Create New Project button located at the top right corner.

4. A popup form titled Create Project will appear.

5. Enter the following details:

Field	Description
Name	Provide a unique name for your project.
Description	Optionally, add a description for better clarity.
Project Prefix	Specify a prefix that aligns with your project standards. This will act as a short identifier.
Project Type	Select ABAP Cloud as the project type.

1. To the right of each project, click on the action button (three dots).

2. Click on Switch To Project to navigate to the configuration page of the selected project.

1. Navigate to the Project Settings page. Click the Environments tab.

2. Click + Add (top-right of the Environments table).

3. Select the desired environment and click Select.

4. If this environment is the source for deployments or synchronization, check the Source checkbox.

Manage User Roles and Permissions

• Go to the Users tab.

• Click the Edit (lock) icon next to the user.

• Check the Deploy checkbox for relevant environment(s).

Build Pipeline Configuration in ReleaseOwl

Step 1: Create a New Build Pipeline

1. Navigate to Build Pipelines in the ReleaseOwl dashboard.

2. Click New Build Pipeline.

1. Select Create New Build Pipeline.

2. Click Create.

1. Enter the Pipeline Name (as per your naming convention).

2. Click Next (Step 2).

Step 2: Configure Environment Details

1. Select the registered ABAP Environment.

2. For the Software Component Name:

   • Go to Manage Software Components in ABAP Cloud.

   • Copy the exact Software Component Name.

   • Paste it into the Software Component field in ReleaseOwl.

• For the Branch Name:

  • In the Software Component details, locate the available branch.

  • Copy the required branch name.

• Paste it into the Branch field.

• Click Next (Step 3).

Step 3: Quality Checks Configuration

1. In this step, enable ATC Checks to perform static code analysis and ensure compliance with coding standards, performance, and security guidelines.

2. Enable ABAP Unit Test Checks to execute automated unit tests and validate the functional correctness of the code.

3. These checks help maintain code quality and prevent defective or non-compliant code from progressing in the pipeline.

• For the ATC Service Key, select Software Component Integration (SAP_COM_0510).

• For the Unit Test Service Key, select ABAP Unit Test Integration (SAP_COM_0735)

1. Click Next (Step 4) to continue.

Step 4: Execution Settings

1. Choose the execution mode:

   • Manual (triggered manually), or

   • Scheduled (runs at defined intervals).

2. Click Next.

3. Enter the required Email ID(s) for notifications.

4. Click Save.

Run the Build Pipeline

After saving:

1. Select the created Build Pipeline.

2. Click Build Now to trigger the execution.

3. The system will display the status of the latest build (Success or Failure).

Release Pipelines

Release Pipelines in ReleaseOwl facilitate orchestrated deployments to SAP environments with structured approval workflows. A pipeline can consist of one or more stages, each representing a deployment phase (e.g., Dev, QA, Prod). Within each stage, users can define a sequence of actions including approval tasks, manual interventions, deployment steps, external callouts, and automated test executions—ensuring controlled and auditable releases across the landscape.

Creating a Release Pipeline

Creating a Release Pipeline is a three-step process.

Step 1	Enter a name in Release Pipeline Name
Step 2	Click 'Add Stages' to add the required stages. Add various types of pre-deployment, deployment, and post-deployment tasks as needed.
Step3	Specify the email ids to receive notifications about release pipeline execution status.

For creating release pipeline:

1. Navigate to Release and click on the Release Pipelines.

2. Click Create New Release Pipeline.

1. Enter the release pipeline name

1. Click Add Stage.

1. Tasks: Click Add to enter any tasks that are to be performed

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

1. Different tasks that can be added are as follows:

Note: All the tasks except Deployment Task are similar for any project type. For CPI projects, Wait for Promotion and Validation tasks are the two extra tasks available other than the ones available for every project type.

Deployment Task

The Deployment Task in the Release Pipeline is responsible for deploying the validated software component to the configured SAP BTP ABAP Environment.

Name	Enter any name of your choice for the approval task being created.
Description	Any message that is to be conveyed for the deployment.
Select Environment	Choose the registered ABAP Environment (e.g., QA or Production).
Component Name	Enter the Software Component name exactly as maintained in ABAP Cloud
Branch Name	Enter the corresponding Git branch (e.g., main).
Schedule Time	You can execute a Release Pipeline either manually or can schedule it to get executed automatically once its reference build pipeline gets executed successfully.

Run the Release Pipeline

1. After creating the pipeline, click Run.

2. Enter the Cycle Name.

3. Select the corresponding Build.

4. Trigger the pipeline execution.

The release process will execute according to the defined stages and tasks, ensuring a controlled and auditable deployment across environments.

Action Button

Edit : Use Edit to modify the existing build pipeline configuration. This option allows you to update details such as the repository, branch, build type, schedules, or any pipeline-related settings. Changes made here affect the same pipeline.

Commits : The Commits option lets you view the list of code commits associated with this build pipeline.

Save as: Use Save As to create a copy of the existing build pipeline.

Archive : The Archive option is used to deactivate the build pipeline. Archived pipelines are not deleted but are removed from active use.