Configuring Pass Conditions for Pipelines

Procedure

You can add pass conditions for a stage where there is a code check task. If the code check result meets the pass conditions, the pipeline continues to run. Perform the following procedure.

• Step1: Create a Rule and Configure Thresholds
• Step 2: Create a Policy and Add a Rule to the Policy
• Step 3: Configure a Pipeline
• Step 4: Execute the Pipeline

Preparations

• You have created a project. The following uses a Scrum project named Project01 as an example.
• You have created a code repository in the project. The following uses a repository named repo01 (created using the Maven template) as an example. (You can choose to automatically create a code check task.)
• You have created a code check task with the repo01 repository. The following uses a code check task named check01 as an example.
• You have created a build task with the repo01 repository. The following uses a build task named build01 (created using the Maven template) as an example.
• You have created a pipeline with the repo01 repository. The following uses a pipeline named pipeline01 (created using the blank template) as an example.

Step1: Create a Rule and Configure Thresholds

1. Log in to CodeArts.
2. Click the avatar icon in the upper right corner and choose All Account Settings from the drop-down list.
3. In the navigation pane on the left, choose Policy Management > Rules.
4. Click Create Rule. On the displayed page, configure parameters.
   Figure 1 Creating a rule
   

   Table 1 Rule parameters

   Parameter	Description
   Name	Enter a rule name, for example rule01.
   Type	Select the rule type Check.
   Extension	Select the extension Check.
   Version	Select the version 0.0.1.
   Threshold Configuration	The extension thresholds are automatically filled based on the selected extension version. You can use the default values.

5. Click Confirm.

Step 2: Create a Policy and Add a Rule to the Policy

There are tenant-level policies and project-level policies. Tenant-level policies can be applied to pipelines of all projects under the current tenant, while project-level policies can be applied to all pipelines under the current project. The following uses a tenant-level policy as an example.

1. In the navigation pane on the left, choose Policies.
   

   A system policy exists by default. You can view and use the policy, but cannot edit or delete it.

2. Click Create Policy. On the displayed page, enter a policy name policy01 and select the rule rule01 created in step 1.
   Figure 2 Creating a policy
   
3. Click Confirm.

Step 3: Configure a Pipeline

1. On the top navigation bar, click Homepage.
2. Search for the project created in Preparations and access the project.
3. In the navigation pane on the left, choose CICD > Pipeline.
4. Search for the pipeline created in Preparations, click in the Operation column, and select Edit. The Task Orchestration page is displayed.
5. In stage 1, add the code check task created in Preparations, click , add Pass-Conditions-of-Standard-Policies, and select the policy policy 01 created in step 2.
   Figure 3 Adding pass conditions
   
6. Click or to add a new stage for the pipeline and add the build task created in Preparations to the new stage.
   Figure 4 Configuring a pipeline
   

Step 4: Execute the Pipeline

1. After configuring the pipeline, click Save and Run.
2. After execution, the code check task passes the verification and the pipeline proceeds to the next stage.
   Figure 5 Executing a pipeline