Fixing a Bug for Quick Release Through a Change-triggered Pipeline

Overview

CodeArts Pipeline provides the microservice model for enterprises. Each microservice is independently developed, verified, deployed, and rolled out, accelerating requirement release. This model also lets enterprises organize teams by function, optimize management models, and improve operation efficiency.

Using this model, you can create change-triggered pipelines to associate them with change resources and release changes for quick project delivery.

Procedure

The following describes how to use a change-triggered pipeline to fix a bug for quick release.

Step 1: Create a Microservice

Step 2: Create a Change-triggered Pipeline

Step 3: Create a Change

Step 4: Execute a Change-triggered Pipeline

Preparations

• You have created a project. The following uses a Scrum project name Project01 as an example.You have created a work item in the project. The following uses a bug work item named BUGFIX as an example.
• You have created a code repository. The following uses a repository named Repo01 (created using the Java Maven Demo template) as an example.
• You have created a CodeArts Repo HTTPS service endpoint. The following uses an endpoint named HttpsEndpoint01 as an example.

Step 1: Create a Microservice

1. Log in to the Huawei Cloud console.
2. Click in the upper left corner of the page and choose Developer Services > CodeArts Pipeline from the service list.
3. Click Access Service.
4. Click Homepage from the top navigation pane.Search for the project created in Preparations and access the project.
5. In the navigation pane on the left, choose CICD > Pipeline.
6. Click the Microservices tab.
7. Click Create Microservice. On the displayed page, configure parameters.

   Table 2 Microservice parameters

   Parameter	Description
   Project	Keep the default value, which is the project of the microservice.
   Microservice Name	Enter Microservice01.
   Code Source	Code source associated with the microservice. Select Repo.
   Repository	Select the repository Repo01 created in Preparations.
   Default Branch	Select master.
   Language	Development language for the microservice. Select Java.
   Description	(Optional) Enter a microservice description.

8. Click OK.

Step 2: Create a Change-triggered Pipeline

1. In the microservice list, click a microservice name. The Overview page is displayed.
2. Switch to the Pipelines tab.
3. Click Create Pipeline. On the displayed page, configure parameters.

   Table 3 Pipeline parameters

   Parameter	Description
   Project	Keep the default value, which is the project of the pipeline.
   Name	Use the default name.
   Code Source	Keep the default value, which is the same as that of the microservice.
   Repository	Keep the default value, which is the same as that of the microservice.
   Default Branch	Keep the default value, which is the same as that of the microservice.
   Repo Endpoint	This is mandatory if you enabled Change-based Trigger. Select the authorization endpoint HttpsEndpoint01 created in Preparations.
   Alias	(Optional) If an alias is set, the system parameters are generated for the repository.
   Change-based Trigger	Enable it to set current pipeline to a change-triggered one. It is enabled in this example.
   Description	(Optional) Enter a pipeline description.

   NOTE:

   Change-triggered pipelines can only be triggered by changes. A microservice can only have one change-triggered pipeline.

4. Click Next and select the Maven-Build template. Stages and jobs will be generated. You can retain the default settings.
5. Click Save.

Step 3: Create a Change

1. Access the created microservice.
2. Click the Changes tab.
3. Click Create Change. On the displayed page, configure parameters.

   Table 4 Change parameters

   Parameter	Description
   Change Subject	Enter fix-a-bug.
   Repository	Keep the default value, which is the same as that of the microservice.
   Branch	The development branch for the change. After the change is successfully released through the pipeline, the branch will be automatically merged to the default branch of the microservice. Select Pull new from default and enter the branch name bugfix.
   Associated Work Item	Select the work item BUGFIX created in Preparations.

4. Click OK.

   After the change is created, the system creates a feature branch based on the microservice default branch. You can commit code to this feature branch.

Step 4: Execute a Change-triggered Pipeline

After the code is updated, you can execute the change-triggered pipeline.

1. On the change list page, click the change name.
2. Click Submit for Release in the upper right corner. In the displayed dialog box, confirm the release.
   Figure 1 Submitting for release
   

3. Click OK. The release list page is displayed.
4. Click Execute in the upper right corner. In the displayed dialog box, select the submitted change, and retain the default settings.
   Figure 2 Execution configuration
   

5. Click Execute.

   During pipeline running, the MergeReleaseBranch and MergeDefaultBranch stages are automatically generated. The newly pulled feature branch is merged to the integration branch.

   After the code check and build jobs are successfully executed, the pipeline proceeds to the MergeDefaultBranch stage with a confirmation dialog box displayed.

6. Click Continue. After the MergeDefaultBranch stage is executed, the system:
   • Updates the change status to Released.
   • Updates the status of the BUGFIX work item to Closed.
   • Merges the code on the release branch to the default branch.

   A change release has been completed.