## 4.2.14.1.5.5  Build
As an add-on administrator, you have two options for triggering the add-on build process. The recommended approach is to use the Build Product Version app in the Landscape Portal to configure and execute an add-on build pipeline, leveraging the CI/CD service on SAP BTP. Alternatively, you can implement your own pipeline manually and run it on an existing CI/CD server. In both cases, a successful pipeline execution will result in a new product version that can be installed.
The add-on build pipeline runs through multiple steps:
- For the add-on assembly, an assembly system is created in the 03 Build/Assemble subaccount. All software components that are part of the add-on product are imported into the system.
##  Note
The import in the assembly system is enabled by communication scenario API for Managing Software Components (SAP\_COM\_0948).
- Before the add-on build, it is possible to execute ATC checks and AUnit test runs in the assembly system.
##  Note
The ATC checks in the assembly system are enabled by communication scenario ABAP Test Cockpit - ATC Run Integration (SAP\_COM\_0901). The AUnit test runs in the assembly system are enabled by communication scenario ABAP Unit Test Integration (SAP\_COM\_0735).
- During the add-on build, delivery packages corresponding to included software component versions are created. For the add-on product version, a target vector is created and published in test scope. See Target Vector
##  Note
The build process is enabled by communication scenario Software Assembly Integration (SAP COM 0582).
- To ensure that the add-on provisioning works correctly, an installation test system is provisioned in the 04 Build/Test subaccount. The new product version is installed using the target vector published in the build stage.
##  Note
The installation test system uses the service plan saas\_oem , enabling the add-on installation.
- Once the build and test installation have been completed successfully, the target vector is published in production scope.
- After a successful build, all ABAP systems used are deprovisioned (unless otherwise specified) and the add-on is technically available for deployment to the ABAP environment.
With any new add-on, it is required that you first register the add-on product and any global accounts you wish to use before building your initial product version.
##  Tip
For in-depth information about the ABAP environment pipeline used for add-on build, check out ABAP Environment Pipeline.
## Prerequisites
- Using the Build Product Version app requires an existing CI/CD subscription in the same subaccount as the Landscape Portal subscription (recommended option). If you used the Booster for Landscape Portal [page 1229] to set up your landscape, then this is already configured.
- Using a custom pipeline configuration and Jenkins server requires the following (not recommended):
- To execute the pipeline, you have to set up a Jenkins CI/CD server and you need an S-user in SAP One Support Launchpad with user management authorization. See Jenkins , Custom Jenkins Setup , and SAP note 1271482 .
- To configure the pipeline, you need to create a configuration repository and implement the add-on build scenario. See Build and Publish Add-on Products on SAP BTP ABAP Environment .