Help Center/ ServiceStage/ User Guide/ Release Management/ New Release Management/ Creating a Region Release Task/ Creating a Region Release Task Using Manual Configurations
Updated on 2025-08-12 GMT+08:00

Creating a Region Release Task Using Manual Configurations

ServiceStage supports up to 1000 region release tasks in the same project.

Create a region release task using manual configurations to combine applications, components, and build tasks in the same region in different phases as required and orchestrate and release them.

Procedure

  1. Log in to ServiceStage.
  2. Choose Release Management.

    • If the Release Management page of the new version is displayed by default, go to 4.

      Overview describes release management of the new version.

    • If the Release Management page of the old version is displayed by default, go to 3.

      Overview describes release management of the old version.

  3. Click Try new edition now or Try New Edition to switch to the Release Management page of the new version.

    The data of the old and new versions are isolated. Switching them will not cause release task data loss.

  4. Choose Region Release Tasks.
  5. Click Create Release Task and set release task parameters by referring to the following table.

    Parameter

    Description

    Release Task

    The release task name must be unique in the same enterprise project.

    Enter 2 to 64 characters. Start with a letter and end with a letter or digit. Only use letters, digits, underscores (_), and hyphens (-).

    Enterprise Project

    Enterprise projects let you manage cloud resources and users by project.

    It is available after the function is enabled. For details, see Enabling the Enterprise Project Function.

    • Click the drop-down list to select an existing enterprise project.
    • Click Create Enterprise Project to create an enterprise project and select it. For details, see Creating an Enterprise Project

    Description

    Description of a release task.

    1. Click .
    2. Enter up to 128 characters.
    3. Click .

    Release Scenario

    Fixed to Custom Orchestration, indicating to customize the orchestration of tasks under a release task. This is used for heavy or stable traffic.

    Example

    Whether to use the example to create a release task.

    • If it is not selected, the example is not used to create a release task.
    • If it is selected, the example is used to create a release task.
      • Simple Example: Automatically add a build model and select an existing build task created by the system.
      • Common Example: Automatically add the build-upgrade component model, select an existing build task created by the system, and use the generated software package or image package as the source of the software package or image package of the component to be upgraded in the component upgrade task.

  6. Click OK.
  7. Configure the release task phase and task.

    • If Example is not selected in 5, go to 8.
    • If you select Example and Simple Example in 5, go to 9.
    • If you select Example and Common Example in 5, go to 10.

  8. If Example is not selected in 5, perform the following operations:

    1. Set Best Effort Policy.
      • Enable it to continue releasing other components when a component fails to be released.
      • If it is disabled, the release task fails when a component fails to be released.
    2. Click next to the phase name and enter a Phase Name, for example, Create Application.
    3. Click Create Task and create a task by referring to Table 1.
      Table 1 Creating a task

      Task Type

      Description

      Create Application

      Add an application creation task to the release task.

      1. Use either of the following methods to go to the Create Application page:
        • Choose All > Create Application > Create Now.
        • Choose Application Management > Create Application > Create Now.
      2. Enter a task name containing 1 to 64 characters.
      3. Enter an application name.

        The application name must be unique in the same enterprise project.

        Enter 2 to 64 characters. Start with a letter and end with a letter or digit. Only use letters, digits, underscores (_), and hyphens (-).

      4. Select an enterprise project.

        Enterprise projects let you manage cloud resources and users by project.

        It is available after the function is enabled. For details, see Enabling the Enterprise Project Function.

        • Click the drop-down list to select an existing enterprise project.
        • Click Create Enterprise Project to create an enterprise project and select it. For details, see Creating an Enterprise Project
      5. Click , enter up to 128 characters as the description, and click .
      6. Click OK.

      Create Component

      Add a component creation task to the release task.

      1. Use either of the following methods to go to the Create Component page:
        • Choose All > Create Component > Create Now.
        • Choose Application Management > Create Component > Create Now.
      2. Select the application to which the component belongs from the Application drop-down list.
      3. Select a component creation method.
        • Create Component: Go to 4.
        • Clone Component: Go to 5.
      4. Click Create Component and perform the following operations to create a component:
        1. Enter a task name containing 1 to 64 characters.
        2. (Optional) Select a task in the previous phase that can be associated with the current task from the Associated Task drop-down list.

          For example, select the Create Application task created in the previous phase.

        3. Set component parameters. For container-deployed components, see Creating a Component Based on a Container Using Manual Configurations. For VM-deployed components, see Creating a Component Based on a VM.

          If you specify Associated Task, for example, the Create Application task created in the previous phase, the Application of the component is fixed to the application set in the selected Create Application task.

        4. Click Deploy Now.

          Select a created component from the component list and click Set to reset component parameters.

          Select a created component from the component list and click Remove to remove the component from the component creation task.

        5. Go to 6.
      5. Click Clone Component and perform the following operations to configure the component:
        1. Select the component to be cloned from the component list and click OK.
        2. Click the component to be cloned in the component list and click Set to reset component parameters.

          For container-deployed components, see Creating a Component Based on a Container Using Manual Configurations. For VM-deployed components, see Creating a Component Based on a VM.

        3. Go to 6.
      6. Click OK.

      Update Component

      Add a component upgrade task to the release task.

      1. Use either of the following methods to go to the Update Component page:
        • Choose All > Update Component > Create Now.
        • Choose Application Management > Update Component > Create Now.
      2. Select the application to which the component belongs from the Application drop-down list.
      3. Set the component image source.
        • If you enable Image from Build, you need to create a build task in the phase before the current task phase. Go to 4.
        • If you disable Image from Build, go to 5.
      4. If you enable Image from Build, perform the following operations:
        1. Click Add Component and select only one container-deployed component to add to the upgrade task.

          The component status is Running, Not ready, or Abnormal. For details about how to check the component status, see Viewing Component Details.

        2. Click OK.

          You can click Change to reselect a component.

        3. Select a build task from the Build drop-down list as the component image source for component upgrade.

          By default, the archive address of the image package output during component upgrade is the archive address set in the selected build task displayed in the Build Output drop-down list.

        4. Go to 6.
      5. If you disable Image from Build, perform the following operations:
        1. Click Select Components to Upgrade and select the component to be added to the upgrade task.

          The component status is Running, Not ready, or Abnormal. For details about how to check the component status, see Viewing Component Details.

        2. Click OK.

          You can click Remove on the card of a component in the list of selected components to be upgraded to remove the component from the list.

          Click Set on the card of the specified component in the list of selected components to be upgraded, enter a Task Name containing 1 to 64 characters, set component upgrade parameters by referring to 5 to 6 in Upgrading Components in Batches, and click OK.

        3. Go to 6.
      6. Click OK.

      Build

      Add a job created for building images from source code, or a JAR, or WAR package to the release task.

      1. Use either of the following methods to go to the Build page:
        • Choose All > Build > Create Now.
        • Choose Application Management > Build > Create Now.
      2. Enter a task name containing 1 to 64 characters.
      3. Select a build task from the Build drop-down list.
      4. Click OK.

      Manual Approval

      Add a manual approval checkpoint task to the release task. If manual approval is set, the release task process can continue only after being approved by related approvers.

      1. Use either of the following methods to go to the Manual Approval page:
        • Choose All > Manual Approval > Create Now.
        • Choose Checkpoint Tasks > Manual Approval > Create Now.
      2. Enter a task name containing 1 to 64 characters.
      3. Select the approver of the release task process from the Approved By drop-down list.

        If the approver list cannot be obtained, contact the administrator to create a custom policy that has the iam:users.listUsers permission of IAM, and bind the policy to the user group to which the current account belongs.

      4. Set Approval Mode.
        • Approved by all: The release task process can continue only after all selected approvers approve the task. Otherwise, the release fails.
        • Approved by any person: The release task process can continue after being approved by any of the selected approvers.
      5. Click OK.

      Manual Trigger

      Add a manual triggering task to the release task. If manual triggering is set, the release task process can continue only after you manually confirm it.

      Use either of the following methods to create a manually triggered task:
      • Choose All > Manual Trigger > Create Now.
      • Choose Checkpoint Tasks > Manual Trigger > Create Now.
      • After a task is created, you can click Create Parallel Task to create a group and task in the current phase by referring to Table 1.
      • Move the cursor to a specified task card in a group, click , and insert a new sequence to execute the tasks in the group by referring to Table 1.
      • Move the cursor to a specified task card and click to delete the task.
    4. Click next to the phase name to create a phase and create a group and task by referring to 8.

      To delete a specified phase, click next to the phase name and click OK. Deleting a phase will delete all groups and tasks in the phase.

    5. Go to 11.

  9. If you select Example and Simple Example in 5, perform the following operations:

    1. Set Best Effort Policy.
      • Enable it to continue releasing other components when a component fails to be released.
      • If it is disabled, the release task fails when a component fails to be released.
    2. (Optional) Click and enter a phase name.
    3. Click Create Build Task and add a job created for building images from source code, or a JAR, or WAR package to the release task.
      1. Enter a task name containing 1 to 64 characters.
      2. Select a build task from the Build drop-down list.
      3. Click OK.
    4. Go to 11.

  10. If you select Example and Common Example in 5, perform the following operations:

    1. Set Best Effort Policy.
      • Enable it to continue releasing other components when a component fails to be released.
      • If it is disabled, the release task fails when a component fails to be released.
    2. (Optional) Click next to the Build phase and enter a phase name.
    3. Click Create Build Task and add a job created for building images from source code, or a JAR, or WAR package to the release task.
      1. Enter a task name containing 1 to 64 characters.
      2. Select a build task from the Build drop-down list.
      3. Click OK.
    4. (Optional) Click next to the Upgrade Component phase and enter a phase name.
    5. Click Create Component Upgrade Task to create a component upgrade task.
      1. Select the application to which the component belongs from the Application drop-down list.
      2. Click Add Component.
      3. Select the component to be upgraded under the selected application.

        Only one container-deployed component whose status is Running, Not ready, or Abnormal can be added to the upgrade task. For details about how to check the component status, see Viewing Component Details.

      4. Click OK.
      5. Select the build task created in the previous step from the Build drop-down list as the component image source for component upgrade.

        By default, the archive address of the image package output during component upgrade is the archive address set in the selected build task displayed in the Build Output drop-down list.

      6. Click OK.
    6. Go to 11.

  11. Perform subsequent operations based on whether to release the release task.

    • If yes, click Save and Execute, select the task to be executed, and click Execute.
      If a checkpoint task is set in the release task, approve the task based on the checkpoint task type by referring to the following table.

      Checkpoint Task Type

      Approval Procedure

      Manual Approval

      1. Click the release task to be executed. The Release Process View page is displayed.
      2. Move the cursor to the card of the manual approval task to be approved.
      3. Click Approve. The Manual Approval dialog box is displayed.
      4. Enter Comments to determine whether to pass the approval.
        • Click Reject to terminate the release task. The release task fails to be released.
        • Click Agree to continue the release.

      Manual Trigger

      1. Click the release task to be executed. The Release Process View page is displayed.
      2. Move the cursor to the card of the manual triggering task to be approved.
      3. Click Approve. The Manual Trigger dialog box is displayed.
      4. Determine whether to pass the approval.
        • Click Reject to terminate the release task. The release task fails to be released.
        • Click Agree to continue the release.
      • On the Release Process View page, you can view the execution status of the release process and wait until the release task is complete.
      • After the release task is saved, its Release Status is Initialized. For details about how to check the release task status, see Viewing Region Release Task Details.
      • After the release task is saved, you can manage the release task by referring to Managing Region Release Tasks.
    • If no, click Save.