Remotely Building a Project
Use the Remote-Multi-Build Ant task to remotely build a project. When a project is built remotely, Mobile Designer transmits the source code to Mobile Administrator. After receiving the source code, Mobile Administrator builds the project on a Mobile Administrator build node that is running the version of Mobile Designer that you specify. The final binaries from the build are made available on Mobile Administrator and can be installed via the Mobile Administrator App Store.
To remotely build a project
1. In Software AG Designer, open the project you want to remotely build.
2. Click the Project Explorer view, expand the project, and drag the build.xml file to the Ant view.
3. In the Ant view, double-click Remote-Multi-Build.
Mobile Designer displays the Remote Multi-Build dialog. This dialog lists only devices for the supported platforms.
If the
mobile.admin.reuse.existing.build_configs property in the ma.properties file is set to
true,
Mobile Designer presets information in the Remote Multi-Build dialog based on build configurations defined in the
Mobile Administrator project that corresponds to this
Mobile Designer project. If multiple build configurations exist,
Mobile Designer uses the latest version.
4. In the Selected column, select the check boxes for each device for which you want to remotely build the project.
Important: | When downloading an application from Mobile Administrator, Mobile Administrator only displays one version per platform. As a result, it is recommended that you select only the universal device for a platform. If you build for a specific device, a user that is using the same platform, but a different device might download an incompatible application. |
If the
mobile.admin.reuse.existing.build_configs property is set to
true,
Mobile Designer preselects each device for which there is a build configuration.
5. In the Target name column, specify the name of the target device you want to remotely build.
Important: | Be sure names you specify match the names in the build configurations of the corresponding Mobile Administrator project. |
If the
mobile.admin.reuse.existing.build_configs property is set to
true,
Mobile Designer specifies device names from build configurations.
6. Leave the information in the Languages column as is.
You cannot configure the languages to use for the build. Mobile Administrator sets the language using the first language specified on the project.handset.handset.langgroups project property. For example, if the project.handset.ios_apple_universal.langgroups property is set to en;de, Mobile Administrator uses en.
7. In the API SDK column, specify the platform SDK that you want to use for compiling.
If the
mobile.admin.reuse.existing.build_configs property is set to
true,
Mobile Designer presets this field to the platform SDK specified in the build configurations.
8. In the Certificate column, specify how to sign the mobile application.
For an Android devices, specify a certificate to use for signing.
For iOS devices, specify the Provisioning Profile to use for signing.
If the
mobile.admin.reuse.existing.build_configs property is set to
true,
Mobile Designer presets this field based on the information in the build configurations.
9. In the MD SDK column, specify the version of Mobile Designer you want to use to build the project, for example, 8.2.7.1.353.
Important: | Be sure a Mobile Administrator build node running the version of Mobile Designer you specified exists. If no such build node exists, the remote build job will remain in a PENDING status indefinitely. |
If the
mobile.admin.reuse.existing.build_configs property is set to
true,
Mobile Designer presets this field based on the information in the build configurations.
10. In the Retain output column, select the check box if you want to retain the platform code the remote Mobile Designer generates on the build node.
If the
mobile.admin.reuse.existing.build_configs property is set to
true,
Mobile Designer presets this field based on the information in the build configurations.
11. Leave the Upload data method field as is.
This field describes how Mobile Designer transmits the source code for the project to Mobile Administrator. To transmit the source code, Mobile Designer compresses the project files and folders you specify into a .zip file and sends the .zip file to Mobile Administrator. You specify the source code files and folders that you want to transmit to Mobile Administrator using the following Mobile Administrator plug-in properties:
12. Update the Version field, if necessary.
When
Mobile Designer displays the Multi-Build dialog, it sets the version based on the
mobile.admin.upload.version property in the ma.properties file.
13. Click Remote Multi-Build.
Mobile Designer display status information for the job in the Remote Multi-Build dialog. For more information, see
Monitoring Jobs Used to Remotely Build
Projects.
