HarmonyOS NEXT release management

About this task

HarmonyOS NEXT release management includes the following features:

• Add or upgrade resources.

• Create and modify release tasks for new deployment packages.

• Create various types of release tasks for deployment packages, such as whitelist canary, time-window canary, and official releases. You can create multiple release tasks for the same version of a deployment package.

• Filter upgrades based on multiple conditions, such as city, device model, device system version, network, and deployment package version.

Add a deployment package

In the mPaaS console, complete the following steps:

1. In the left navigation pane, click Real-time Release > Release Management. The release management page opens.

2. Click +Add Deployment Package. In the window that appears, configure the following settings:

   • Platform: Select Harmony.

   • Release Type: Select AppGallery. This allows the app downloaded from the HarmonyOS AppGallery to prompt users for an upgrade. To use this feature, you must first list your app in the HarmonyOS AppGallery.

   • AppGallery URL: The URL of your app in AppGallery.

   • Version Number: The version number of the deployment package.

   • Release Description (Optional): The description of the deployment package.

3. Click OK. The new deployment package is added and appears at the top of the page.

4. In the release management list, click the plus icon () next to a deployment package to view its release tasks:

   • If a deployment package has not been released, its status is To be released and it has no associated release tasks.

   • If a deployment package has been released, its status matches the status of the latest task, and it has associated release tasks.

Create a release task

You can create release tasks for a deployment package that you have added. You can create multiple release tasks for the same version of a deployment package. A single deployment package can have a maximum of 10 active release tasks at the same time.

Release task delivery rules:

• When a client request matches multiple release tasks, the task for the higher version is delivered first.

• If a client request matches multiple release tasks for the same deployment package version, the delivery priority is based on the task type, from highest to lowest: Official > Whitelist (Canary) > Time-window (Canary).

• If the deployment package version and task type are the same, the most recently created task has priority. For example, you create a whitelist task A for version 5.0 in the console, which performs a one-time upgrade for version 4.0. Then, you create another whitelist task B, which performs a forced upgrade for version 4.0. If both tasks are active, when a client with version 4.0 requests an upgrade, task B is delivered first. After task B is stopped or paused, task A is delivered.

• When both a canary task and an official task are active for the same version, the release status in the list is Official Release. After the official task is paused or ended, the release status changes to Canary Release. If all tasks have ended, the status is Release Ended.

Procedure:

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

2. In the Operations column on the right, click Create Release Task.

3. On the Create Release Task page, select or enter the following information:

   • Release Type: Can be Canary or Official.

     • Canary: A small-scale release to a subset of users to verify that the new package features work as expected before an official release.

     • Official: An official release to all users.

   • Upgrade Mode: Can be One-time, Multiple, or Forced.

     • One-time: Prompts the user to upgrade after the app starts, according to the silence policy.

       Note

       A silence policy means that after a user clicks Cancel on an upgrade prompt, the app enters a silence period during which the prompt is not shown again. The default silence period is 3 days, but this is customizable. For more information, see Release a new version using the SDK.

     • Multiple: Prompts for an upgrade every time the app starts.

     • Forced: Prompts for an upgrade every time the app starts, and the prompt window cannot be closed.

   • Release Model (Canary releases only): Can be Whitelist Canary or Time-window Canary.

     • If you select Whitelist Canary, you must configure a whitelist.

       Note

       You can configure whitelists on the Whitelist Management page. For more information, see Whitelist Management.

     • If you select Time-window Canary, you must specify the End Time and Number of Canary Users.

   • Upgrade Prompt Message (Optional): The message displayed during the upgrade.

   • Release Description (Optional): A description of this release task.

   • Advanced Rules (Canary releases only): Click Add. In the window that appears, you can choose to Include or Exclude devices based on criteria such as City, Device Model, and Network. For each criterion type, you must select a corresponding Resource Value.

4. After you configure the settings, click OK to start the release. You can click the plus icon () next to the deployment package to view the newly created release task.

   Note

   Currently, the HarmonyOS NEXT system does not support canary release features.