Managing Apps : Managing the Builds of an App : Managing the Build Configurations of an App : Adding a Build Configuration
Adding a Build Configuration
When you add a build configuration - for example, for an app which runs on iOS - you can determine which version of the SDK on a build node is to be used to build the app, the provisioning profile that is to be used in the build, and the policies that are to be built into the app. Policies on iOS can disable copy and paste within the app or force authentication before the app can be used.
In addition to the app policies, you can also define the users who are to receive notifications in the case of successful or failed builds.
Note:  
When you add a build configuration, you have to specify a certificate for the platform to be used. If you have not yet uploaded the required certificate, see the appropriate section in Configuring Mobile Administrator.
To add a build configuration
1. Click .
2. Click the app for which you want to add a build configuration
3. Click Build on the left side.
4. On the Build Configurations tab, click .
5. Specify the following information:
Options
Description
Platform
Select the platform for which you want to create the build configuration (for example, iOS or Android).
Build node
Select the build node that is to be used. The drop-down list box provides for selection the build nodes that have already been set up. Defined build nodes that are currently not available are marked as "(offline)" in the drop-down list box. Make sure not to select an offline build node. When you select Auto-select, a build node will be used that meets the requirements (SDK, platform) for running the build job. See also Managing Build Nodes.
Repository
Specify how the source code for the is to be made available. When a source code repository has been defined for the app (see Adding a Source Code Repository, you can select the repository from this drop-down list box. The source code from that repository will then be used automatically when the build configuration is launched. When a source repository has not been defined for the app, it is only possible to select Source code will be uploaded manually. In this case, you have to upload a zip file containing the latest source code before launching the build configuration.
Product stage
Select the product stage. This can be either stable or unstable. See also Managing Product Stages.
Relative Source Path
Optional. Enter the relative path to the source code in the zip file that will uploaded before the build configuration is launched. By default, the slash (/) is used.
Tags
Optional. Enter any tags, separated by a comma. The tags are used to determine the "Related Apps" that are shown when the user displays an app in the app store. They are also considered when searching the app store or when filtering the apps.
Scheduled?
Optional. Only shown when a source code repository has been defined for the app (see above). If selected, the build will automatically be started at the time defined in the Daily Schedule boxes (hour and minute).
Enable commit trigger
Optional. Only shown when a source code repository has been defined for the app (see above). If selected, the build is automatically started when a change is committed to the source code repository. This may occur in addition to the daily schedule.
Override app name
If selected, the app name as defined in the source code is used. If not selected (default), the app name as defined in the app details is used.
Override app icon
If selected, the app icon as defined in the source code is used. If not selected (default), the app icon as defined in the app details is used.
Run tests after build
If selected, all tests that are defined in the source code are run after the build job has finished.
Require tests to pass
If selected, a build job can only receive the status "Success" if all tests have run successfully. If not selected, a build job can receive the status "Success" even if one of the tests has failed.
The remaining options that are shown on this page pertain to the platform you have selected.
6. Specify the options for the selected platform.
*For iOS, specify the following:
Option
Description
iOS Provisioning Profile
Select a provisioning profile that you have previously uploaded. See also Managing Provisioning Profiles.
SDK Version
Select the SDK version that is to be used to build the app. You can select either Any to use the latest version on the build node or you can select a specific version number.
Xcode Schema Name
Optional. Enter the name of an Xcode scheme that is to be used to build the app.
Verbose output
If selected, verbose log output will be generated.
*For Android, specify the following:
Option
Description
Android Developer Certificate
Select a developer certificate that you have previously uploaded. See also Managing Developer Certificates.
API Level
Select the API level that is to be used. You can select either Any to use the latest level on the build node or you can select a specific level number.
Java Version
Select the Java version that is to be used to build the app. You can select either Any to use the latest version on the build node or you can select a specific version number.
*For Windows Phone and Windows 8/RT, specify the following:
Option
Description
Code Signing Certificate
Select a code signing certificate that you have previously uploaded. See also Managing Developer Certificates.
Main Project Name
Optional. Enter the name of the app project that is to be used to build the app.
Note:  
When you select a specific version instead of Any, this version must exist on the build node. Otherwise, you will find a hint in the details of the build job indicating that the build node does not support your selection.
7. Optional. Under webMethods Mobile Designer, select Build using webMethods Mobile Designer if you want to build the app using the Mobile Designer SDK.
If selected, you have to specify the following additional options:
Option
Description
Target Name
Enter the "target device" as defined in Mobile Designer.
SDK Version
Specify the SDK version that is to be used to build the app. Or select Any to use the latest version on the build node.
Retain intermediate build files
Mobile Designer compiles native code in an intermediate step before launching the build. If selected, the files containing the native code are kept.
8. Optional. Under App Policies, select the app policies that are to be applied. Only the policies which pertain to the selected platform are shown. See Overview of App Policies for more information on the enhancements and restrictions that you can define.
9. Optional. Under Custom Build Parameters, specify any parameters that your app requires. Specify the parameters in the following format:
key1=value1, key2=value2, ...
Parameters will be made available as global project parameters (Mobile Designer builds) or precompiler definitions (iOS native builds).
10. Optional. Under Notification Settings, click Add User if a user is to receive a notification after the app has been built. Select the user name from the resulting drop-down list, and then select the check boxes for the types of notifications that the user is to receive (for example, on first failed build).
If you want to remove a user that you have just added, click Remove User and select the user name from the resulting drop-down list.
Note:  
The changes to the list of users are only saved when you save all of your changes by clicking Create Build Configuration.
11. Click Create Build Configuration.
Copyright © 2014-2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback