Mobile Platform as a Service:Manage Android releases

About this task

Android release management provides the following functions:

• Add upgrade resources and provide the QR code of the download link.

• Create and modify the task of the new version resource package.

• Create multiple types of release tasks for added release packages, such as whitelist gray release, time-window gray release, and official release. One upgrade package can have multiple release tasks.

• Support upgrade filtering by multiple criteria, such as the city, model, device system version, network, and release package version.

Add release packages

Log in to the mPaaS console and complete the following steps:

1. On the left navigation bar, choose Mobile Delivery Service > Release management. The release management list is displayed.

2. Click Add a package, and complete the following configuration in the pop-up window:

   • Platform: Select Android.

   • Package: Upload a local .apk release package.

   • Version: Enter the version number of this package, which contains digits and characters.

   • Release description: Describe this release package. Optional.

   • Download verification: When enabled, after the QR code is scanned, the package can be downloaded only after the verification code is verified.

3. Click OK. The new release package is displayed on the top of the list.

   Note: After the release package is added, a QR code is generated in the QR code column for users to download the .apk release package. You can scan the QR code to download the release package to your phone.

4. In the release management list, click the plus icon () in front of the release package to view the release task of the upgrade package:

   • If the upgrade package has never been released, the status of the package is To be released, and there is no release task.

   • If the upgrade package has been released, the status of the package is the release status of the latest task, and there are release tasks.

Create a release task

Create a release task for the added release package. Multiple release tasks are supported for one upgrade package. Up to 10 release tasks are allowed for one upgrade package concurrently.

Rules for delivering release tasks:

• When the client request matches multiple tasks, the higher version task takes priority.

• If a release package have multiple release tasks, by task type, the priority of the tasks is: Formal release > Whitelist gray release > Time window gray release.

• For a specific version release package, if the task type of the release tasks are same, the latest released task shall prevail.

  For example, for version 5.0 upgrade package, a whitelist release task A was created on the console to perform upgrade for version 4.0 app with single reminder; then a whitelist task B was created to perform a forced upgrade for version 4.0. With the two tasks performing at the same time, when a 4.0 version client requests an upgrade, task B is delivered first, and after task B is terminated or suspended, task A takes effect.

• If a grayscale task and a formal task are performed concurrently for a release package, the release status shows “Official release” in the release task list, and when the formal task is paused or ended, the release status changes to “Gray release”. If all tasks are finished, it shows “Finished”.

The operation steps are as follows:

1. Locate the release package for which you want to create a release task.

2. In the Operation column, click Create release task.

3. On the Create a release task page, select or enter the following information:

   • Release type: You can select Gray release and Official release.

   • Upgrade mode: You can select Single, Multiple, and Forced upgrade.

     • Single: After the app is started, it displays an upgrade message based on the silent strategy.

       Note

       Silent strategy means that after the upgrade reminder pops up, after the user cancelled it, the reminder will be in Silent state for a period of time, and no longer reminds the upgrade. The default silent period is 3 days, which can be customized. To customize the silent period, see setIntervalTime.

     • Multiple: The app displays an upgrade message every time it is started. Users can close the message window.

     • Forced upgrade: The app displays an upgrade message each time it is started, and the message window cannot be closed.

   • Release model (only when Gray release is selected): You can select Whitelist gray release and Time-window gray release.

     • If you select Whitelist gray release, you can configure a whitelist below.

       Note: You can configure a whitelist on the Whitelist management page. For more information, see Manage whitelist.

     • If you select Time-window gray release, you can set End time and Users count.

   • Upgrade prompt message: Specify a message to be displayed upon an upgrade. Optional.

   • Release description: Describe this release. Optional.

   • Advanced rule: For Gray release only. Click Add. In the displayed dialog box, select a rule type such as City, Device model, or Network in Type, set Operation type to Include or Exclude, and set Resource value corresponding to the type you selected.

4. After completing the configuration, click OK. To view the release task that you have created, click the plus icon () on the left of the release package.

5. Repeat the steps above if you need to create multiple release tasks.

Other operations

After creating a release task for the upgrade package, you can change the task status.

1. In the release management list, click the plus icon () in front of the release package.

2. Perform the following operation based on your needs:

   • Click Pause to suspend the release task. To continue the task, click Continue.

   • Click End to terminate the release task. After the task is terminated, you can no longer operate it.