- Service Overview
- Getting Started
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Template management
-
Pipeline Management
- Execute Pipeline
- Obtaining Pipeline Status in Batches
- Obtaining the Pipeline Status/Obtaining Pipeline Execution Details
- Obtaining the Pipeline List/Obtaining the Pipeline Execution Status of a Project
- Deleting a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Execution Records
- Creating a Pipeline Using a Template
- Creates a pipeline.
- Re-trial Run Pipeline
- Pass the manual review.
- Reject to Manual Review
- Querying Pipeline Logs
- Manage by group
- Rule Management
- Tenant-level policy management
- Project-level policy management
-
Tenant-level open source governance policy management
- Creating a Tenant-Level Open Source Governance Policy
- Modifying a Tenant-Level Open Source Governance Policy
- Querying Details About a Tenant-Level Open Source Governance Policy
- Querying the Tenant-Level Open Source Governance Policy List
- Deleting a Tenant-Level Open Source Governance Policy
- Changing the Enabling Status of a Tenant-Level Open Source Governance Policy
- Project-level open source governance policy management
-
Extension Plug-in Management
- Creating a Plug-in Version
- Creating a Plug-in Draft Version
- Creating a publisher
- Update Plug-in Draft
- Releasing a Plug-in Draft
- Updating Basic Plug-in Information
- Releasing a Plug-in
- Binding a Plug-in to a Publisher
- Updating the Plug-in Icon
- Updating the Publisher Icon
- Deleting a Plug-in Draft
- Querying the Publisher List
- Querying Available Publishers
- Querying the List of Optional Plug-ins
- Querying the Basic Plug-in List
- Querying the List of Optional Plug-ins in Pagination Mode
- Listing add-ons
- Query Plug-in Indicator Configuration
- Query Plug-in Input Configuration
- Query Plug-in Output Configuration
- Querying All Plug-in Version Information
- Querying Plug-in Version Details
- Querying the Plug-in Version
- Deleting a publisher
- Querying Publisher Details
- Creating a Basic Plug-in
- Updating Basic Plug-ins
- Deleting a Basic Plug-in
- Uploading Basic Plug-ins
- Querying Basic Plug-in Details
- Appendixes
- Change History
-
FAQs
- Functions
-
Troubleshooting
- The Pipeline Parameter Referenced by the Task Does Not Exist
- Test Suite Was Running
- Failed to Obtain Tenant Information During Code Check Task Execution
- The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
- Scheduled Task of a Pipeline Was Not Triggered
- Run Button Was Unavailable
Show all
What Are Pass Conditions?
CodeArts Pipeline provides unified pass condition management. Pass conditions are quality metric thresholds used for automated monitoring in a pipeline. You can configure rules and policies as pass conditions to control pipeline execution.
Currently, only pass conditions of standard policies are supported. When configuring a pipeline, click under a stage. In the Pass Conditions dialog box, move the cursor to the pass condition card and click Add to add the pass condition for this stage, and configure a policy for the pass condition.
- Rules: Set the comparison relationship and threshold criteria for creating and editing policies based on output thresholds of extensions. The comparison relationship and threshold criteria are applied as pipeline pass conditions. Currently, the following extensions are supported:
- Check: You can set thresholds for the problems found in code check results.
If the number of problems is less than or equal to the threshold, the code check is passed and the pipeline continues to run. Otherwise, the code check fails and the pipeline execution is terminated.
- TestPlan: You can set the test pass rate thresholds for APIs in the test suite.
When the pass rate is greater than or equal to the threshold, the test is passed, and the pipeline continues to run. Otherwise, the test fails, and execution of the pipeline is terminated.
- Check: You can set thresholds for the problems found in code check results.
- Policies: a set of rules. Each rule corresponds to a condition template of the output metric value in an extension. You can select policies during pipeline orchestration as pass conditions to control pipeline execution.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.