The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
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.
Troubleshooting FAQs
- 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
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore