Skip to content

Creating a Build Job

Create a build job for the selected application.

A build job merges both project settings , and build settings, such as signing profiles. Select the Create Build Job button to create a build job for Mobile Development Kit Client. For Mobile Card Kit the button only appears if no build job is defined.

As a developer you can configure multiple Custom Mobile Development Kit Client configurations in parallel to experiment with branding and other build settings. You can easily switch between configurations, see the build job status, drill down to the build job details and executions logs, and experiment with installing the app on the device via QR Code.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.

  2. Select an application, then select Cloud Build under Assigned Features (or add it first); or select Features > Cloud Build for Mobile Card Kit.

  3. Select Create Build Job to create a new build job.

    For Mobile Card Kit, only one build job is allowed, so the button does not appear if a build job already exists. You need to either edit the current build job, or delete it and create a new one.

  4. In Create Build Job, select a client type.

    Supported client types include the following:

    • Mobile Development Kit Client
    • SAP Asset Manager
    • Mobile Card Kit Client (SAP Mobile Cards application only)

    For information about the different app types and required packaging details, see Supported Client Types, Packaging Details, and Build Options.

  5. Fill out the basic information for the selected client type. The fields are dynamic and appear depending on the selections you make.

    For information see Supported Client Types, Packaging Details, and Build Options.

  6. Fill out the platform information page.

    • (Mobile Development Kit Client)

      Under Android & iOS Builds, enter the URL Scheme.

      Under Android Builds, enter the Google Services JSON File, or browse to find it.

      Select Show Contents to view the contents of the JSON file. If it is not the right file, click Remove File and try again. Once saved, the JSON file is uploaded.

    • (SAP Asset Manager)

      Under Android & iOS Builds, enter the URL Scheme.

      Under Android Builds, enter the Google Services JSON File, or browse to find it.

      Select Show Contents to view the contents of the JSON file. If it is not the right file, click Remove File and try again. Once saved, the JSON file is uploaded.

  7. On the Multimedia page, identify the launch icon and splash screen icons, depending on the selected app type. You can use the default icon, Upload a new icon following the size guidelines, or click Reset to revert to the default. Click the image title to preview the icon.

    (Android only) If you uploaded the Google Services JSON File, you can upload a custom push notification icon.

  8. (Not applicable to Cordova Hybrid Mobile apps, packaged apps, and custom SAP Fiori Clients created in Web IDE in the Neo environment). Provide the build options:

    • Platforms ‒ the platforms to build, such as Android and iOS.

      Note

      For SAP Asset Manager, both the Android and iOS platforms are supported.

    • Signing Profile ‒ the profiles for the Android and iOS platforms.

      To build an iOS Mobile Card Kit client containing iMessage and Today Screen extensions, choose individual signing profiles for each extension.

      Note

      If an older signing profile reports a Null Object Exception, you must reload the profile.

    • Minimum Platform Version ‒ the minimum operating system version required for the Android and iOS platforms.

    • Build Options ‒ define the type of binary to build.

      • Create Debug-enabled Binaries

      For information about the different build options, see Supported Client Types, Packaging Details, and Build Options.

  9. Select Finish.

Editing a Build Job

Edit a build job for the selected application.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.

  2. Select an application, then select Cloud Build under Assigned Features (or add it first); or select Features > Cloud Build for Mobile Card Kit.

  3. On the Build Jobs tab, select edit for the build job to edit.

  4. Use the Edit Build Job wizard to make changes to the build job. See Creating a Build Job for field definitions. The fields used depend on the client type selected.

  5. Select Finish. The build job Status changes to "Build Required", and the new values are used the next time you run the build.

Enable Detailed Event Logging

Enable or disable detailed event logging for the Cloud Build standalone service on Mobile Services cockpit.

When disabled, error logging continues but the detailed create, read, update, and delete operations are not included.

  1. In Mobile Services cockpit, select Settings > Cloud Build.

  2. Select Enable Detailed Event Log in the upper right corner to start logging the initialization of default purge settings for cloud build. To see the detailed event log related to build process for the cloud build, you need to enable the detailed event log for cloud build feature at the application level (see Viewing Event Logs).

  3. At any time, select Disable Detailed Event Log to stop logging these operations. Error logging continues.

Purge Cloud Build Artifacts

Set up a schedule for purging cloud build logs and build output.

Purging is at the tenant level. Cloud build logs are kept for the number of days that you specify, and purged when the scheduler task runs. Output and artifacts are kept for the number of builds that you specify, and purged when the scheduler task runs.

  1. In Mobile Services cockpit, select Settings > Cloud Build > Purge Settings.

  2. If Enable Purge Settings is disabled, select edit .

  3. Select Enable Purge Settings and edit the purge settings.

    Purge Settings

    Settings Description
    Clear logs of successful builds after Identify when to clear logs for successful builds ‒ Immediately, or after 1, 3, 7, or 30 days. Default is 7 days.
    Clear logs of unsuccessful builds after Identify when to clear logs for unsuccessful builds ‒ Immediately, or after 1, 3, 7, or 30 days. Default is 7 days.
    Keep output of last n successful builds per app Identify how long to keep the artifacts from the last 1-5 successful app builds. Default is 3 successful builds.
    Keep output of last n unsuccessful builds per app Identify how long to keep the artifacts from the last 1-5 unsuccessful app builds. Default is 3 unsuccessful builds.
    Last purge Shows the last successful purge in the YYYY-MM-DD HH:MM:SS format (local or UTC time zone).
  4. Select Save.

The data is kept until the scheduler task runs, typically every 12 hours, unless otherwise configured on the server side. A build with a PENDING status will not be effected by the purge settings.


Last update: September 29, 2020