Build pipeline support for onPrem Fiori
Last updated
Last updated
SAP Fiori applications traditionally require manual transport management via SAP TMS (Transport Management System). However, ReleaseOwl provides an automated pipeline-based approach for deploying Fiori apps on on-premise SAP systems using transport requests. This guide explains how ReleaseOwl streamlines the build, transport, and deployment process for Fiori applications.
Before setting up the UI5 ABAP build pipeline in ReleaseOwl, ensure the following prerequisites are met:
SAP System Access: You need access to an on-premise SAP system with proper authorizations for transport requests.
SAP Git Repository: The source code for the UI5 application must be stored in an SAP Git repository.
Node.js Environment: Ensure that Node.js (preferably version 16 or later) is installed for UI5 build tools.
Transport Package: A valid SAP transport package must be created to deploy the UI5 application.
ReleaseOwl Access: Users must have valid login credentials and required permissions in ReleaseOwl to configure build pipelines.
Log in to ReleaseOwl.
In the left-side navigation panel, go to Build and then select the Build Pipelines.
Click on Create New Build Pipeline
Enter a descriptive Pipeline Name.
Click Next.
Step 3: Connect to Repository
Enter the Repository URL where the UI5 project is stored.
Select the SCM credentials, which are your version control credentials registered in the credential manager.
Select the appropriate Branch containing the UI5 project.
Choose the Version Control Platform.
Click Next to proceed.
Step 4: Configure Build Parameters
In the Builder section, specify the following:
Build Type: It is automatically populated eg: UI5 ABAP
Build Tool Version: Select the build tool version of it
Discard Old Builds: Define the number of previous builds to remove.
Max Builds to Keep: Set a limit for retained builds.
The App Details in the Build Section need to be manually entered based on the information provided in the ui5-deploy.yaml file. Attributes such as App Id, App Name, Description and Package Name should be extracted from the configuration file and entered into the respective fields to ensure accurate deployment.
Step 5: Scheduler and Notifications
Scheduler: Choose Manual, Schedule, or Webhook for pipeline execution.
Notifications: Enter email IDs to receive build alerts.
Tool Integrations: Enable SonarQube and select credentials if needed.
Click Save button.
Step 6: Triggering and Monitoring a Build
After creating the build pipeline, navigate to the Build Pipelines section.
Click the Build Now button to trigger a new build process.
Once the build starts, view its progress and details inside the pipeline.
Clicking on a pipeline name opens a detailed build history, where each triggered build is listed with:
Build Number: The sequential number assigned to each build.
Java/Node Version: The versions used for the build.
Repository & Branch: The source code details.
Triggered By: The user who initiated the build.
Triggered Time: The timestamp when the build started.
Status: Indicates whether the build was successful, failed, o
Clicking the arrow (>) button next to a build allows you to view detailed logs, status, timestamp, and deployment insights.
After a successful build, click the dropdown button to enter a Transport ID.
Select a Transport ID from the list before proceeding with the upload.
Click the Transport button next to the dropdown field in the "Upload to SAPUI5 ABAP Repository" popup.
The "Create WorkBench Transport" dialog appears.
Enter the necessary details to create a WorkBench transport.
Confirm the settings and complete the transport process.
After uploading the build, you can check the Upload Logs, which provide real-time updates on the status of the deployment process.
