CodeArts Pipeline
CodeArts Pipeline
- 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
On this page
Show all
Help Center/
CodeArts Pipeline/
FAQs/
Troubleshooting/
The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
Updated on 2023-11-28 GMT+08:00
Symptom
When you modify the source branch code of an unclosed merge request and commit code, the pipeline that does not listen to the push event is triggered.
Root Cause
- You have configured a merge request for a repository and listened to update events.
- You have created a merge request and the request is not closed.
- When you commit code to the source branch of the merge request, an update event is generated. If the target branch is within the listening range of the merge request, the pipeline is triggered.
Conclusion
When you modify the source branch code of an unclosed merge request and commit code, an update event is generated. If the target branch of the merge request is within the listening range, the corresponding pipeline is triggered.
Parent topic: Troubleshooting
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.