Cloning a Region Release Task Created Using a Release Task Template

Prerequisites

• The region release task has been created using a template. For details, see Creating a Region Release Task Using a Release Task Template.
• You have compressed the prepared release task template files into a ZIP package and uploaded the package to the repository. For details, see Release Task Template Description.
  • Upload the template package to the SWR repository. For details, see Uploading a Software Package.

    If PKIToken is disabled, the SWR repository is not supported.

  • Select the corresponding template package from OBS. Upload the template package to the OBS bucket in advance. For details, see Streaming Upload (PUT).
  • If you need to use JFrog (example) as the repository for storing the template package, you can use an HTTP/HTTPS custom file download address as the template package download address. Upload the template package to the custom file address in advance.

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. Use either of the following methods to go to the page for cloning a release task:
   • Directly clone: Click More > Clone in the Operation column of the target release task.
   • Clone after viewing details: Click the target release task. After Viewing Region Release Task Details, choose ... > Clone in the upper right corner.

6. Set the basic parameters of the release task 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. Click . Enter up to 128 characters. Click .

7. Set Set Template Package by referring to the following table.

   Operation	Procedure
   Removing a template package	Perform the following operations based on the selected template package storage mode: CodeArts release repository: Move the cursor to the added template package card and click . OBS: Move the cursor to the added template package card and click . SWR repository: Move the cursor to the added template package card and click . Custom file address: Select the path of the template package file to be removed and click Delete.
   Adding a template package	Select the uploaded release task template package based on the template package storage mode: CodeArts release repository: Click Select Software Package, select the uploaded template package from the CodeArts release repository, and click OK. OBS: Click Select Software Package, select the uploaded template package from the OBS bucket, and click OK. SWR repository: Click Select Software Package, select the uploaded template package from the SWR repository, and click OK. Custom file address: If you need to use JFrog (example) as the repository for storing the template package, perform the following operations to obtain the template package that has been uploaded to the custom file address: Click Add Custom File Address. Enter the HTTP/HTTPS custom file download address where the software package is located. The custom file address must be the complete path of the release task template package file, for example, https://172.16.0.1:8082/artifactory/template-release.zip. Determine whether to enable authentication. If authentication is disabled, any user can download the software package in the custom file address by default. Click to enable authentication. Only authenticated users can download the software package in the custom file address. Authentication mode can be User name and password authentication or User-defined Header Authentication. The authentication mode and the corresponding authentication parameters are determined by the authentication mode supported by the server where the custom file directory is located.

8. Click Next.
   • In the Preview Template Package area, you can view the details of the release task template file.
   • In the Set Parameters area, you can view and modify the release task parameters.

9. Click Create and Deploy.
   • On the Release Process View page, you can view the release task process details.
   • After the release task is created, its Release Status is Initialized. For details about how to check the release task status, see Viewing Region Release Task Details.
   • After a release task is created, you can manage the release task by referring to Managing Region Release Tasks.