Build the First Version of Your Add-On Product

1.Get the “Org Name”, “API Endpoint” and “Space” for the subaccount 03 Build/Assemble

• As an authorized BTP Cockpit user, navigate to the subaccount 03 Build/Assemble in the Global Account for Development.

• Navigate to the overview section using the menu.

• Note the “API Endpoint”, “Org Name” and the “Space” where you wish for your systems to be created. We shall use this information while configuring our build parameters.

2.Get the “orgname”, “apiendpoint” and “space” for the subaccount 04 Build/Test.

• As an authorized BTP Cockpit user, navigate to the subaccount 04 Build/Test in the Global Account for Development.

• Navigate to the overview section using the menu.

• Note the “API Endpoint”, “Org Name” and the “Space” where you wish for your systems to be created. We shall use this information while configuring our build parameters.

3.Get the relevant CommitID for the software components involved in the build

• As Administrator of the development system where the code for the add-on is developed, open the “Manage Software Components” application from the Fiori Launchpad.

• Find your software component from the list of software components.

• Open the entry for your software component and navigate to the “Branching” section.

• Navigate to the branch where you are developing (In this example, the main branch) to see the list of commits. The “Message” column provides details of the transport request contained in the commit. Identify the commit based on which you wish to build your add-on product.

• Open the entry for the chosen commit to see the Long Commit ID. We will use this while configuring our build parameters.

• In case you have more than one software component in your product, repeat above steps to identify the Long Commit ID for all involved software components.

1.As Landscape Portal Administrator, open the “Build Product Version” application of the landscape portal.

2.Find your product in the list of products displayed and open the entry for it.

3.Under the template section, configure Release Delivery. You could also configure a template for support package or patch delivery for future updates.

4.Configure parameters based on information collected earlier

• Configure parameters for the “Prepare System” phase.
  The API endpoint, Organization and Space are collected from the subaccount 03 Build/Assemble.
  The Credential Name is the name provided while maintaining credentials for the cloud foundry platform user in the previous tutorial of this group.
  The “Keep System” checkbox can be used to configure if the system shall be deleted after the build or kept alive.

Note: Keeping the system alive helps in diagnosing issues faced during a build but could incur additional costs (entitlements locked for the system).

• Configure parameters for Clone, ATC and Build stages as per following screenshots.

• Configure the “Integration Tests” stage like the “Prepare System” stage but with details of the subaccount 04 Build/Test.

1.Open your product in the “Build Product Version” Application of the Landscape Portal.

2.Click the Create button and select Release Delivery (or Support Package/Patch if you are delivering one of these).

Note: The “Support Package Stack” and “Patch Delivery” buttons are only enabled if templates are maintained for them.

3.Add the software components relevant for your product with suitable commit IDs as identified in Step 1.

4.Click “Build Product Version” to start the build.

1.Open the “Build Product Version” application of the Landscape Portal and navigate to your product. Under the “Product Versions” section, you could see the status of the build.

2.For more detailed logs, open the entry for the version you are building. This lists logs for various steps of the add-on build pipeline. Use these logs to diagnose errors that may arise during your builds.