Launching a Build Configuration
When you launch a build configuration, you specify a version and build number. If you have not defined a source code repository in the build configuration, you have to select a zip file which contains the source code. A new build job is then generated which creates a new version of the app.
As long as you are testing your app and its build configuration, it is recommended that you define the product stage "unstable" in the build configuration. Otherwise, the new erroneous version of the app will immediately be available for download in your app store.
To launch a build configuration
1. Click 
. 2. Click the app for which you want to launch a build configuration
3. Click Build on the left side.
4. On the Build Configurations tab, select the build configuration that you want to launch.
5. Specify the version number that you want to assign to the new version.
6. Optional. Specify the build number that you want to assign to the new version. If you do not specify a build number, it will automatically be incremented.
7. If you have not defined a source code repository in the build configuration, click Browse and then select the zip file which contains the source code.
The Browse button is not shown when a source code repository has been defined in the build configuration.
8. Click Launch Selected Build Configs.
A new build job is created. You can view it on the Build Jobs tab. The new version of the app will be shown on the Versions page of the app. Keep in mind that a new version may also be shown there when the build status is "Error" (for example, when the executables are still missing).
If users are to be notified, for example, when a new version is available or when the build has failed (see
Adding a Build Configuration), the notifications are sent.
Note: | If the build job results in the status "Error", you can view the errors and then relaunch the build job after the errors have been corrected. See also Managing Build Jobs. |
