- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- CodeArts Pipeline Usage
- Enabling and Authorizing CodeArts Pipeline
- Accessing CodeArts Pipeline
- Creating a Pipeline
- Configuring a Pipeline
- Grouping Pipelines
- Executing a Pipeline
- Checking a Pipeline
- Checking the Dashboard
- Configuring a Change-triggered Pipeline
- Managing Pipeline Extensions
- Creating Service Endpoints
- Checking Audit Logs
- Reference
- CodeArts Release User Guide
-
Best Practices
- CodeArts Pipeline Best Practices
- Fixing a Bug for Quick Release Through a Change-triggered Pipeline
- Configuring Pass Conditions for Automated Code Checks
- Transferring CodeArts Pipeline Parameters to CodeArts Build and CodeArts Deploy
- Creating a Repository Tag Using the Pipeline Contexts
- HE2E DevOps Practice: Configuring a Pipeline
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Template Management
-
Pipeline Management
- Starting a Pipeline
- Obtaining Pipeline Statuses in Batches
- Obtaining Pipeline Status/Obtaining Pipeline Execution Details
- Obtaining Pipeline List/Pipeline Execution Status in a Project
- Deleting a Pipeline
- Querying Pipeline Details
- Editing a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Execution Records
- Creating a Pipeline With a Template
- Creating a Pipeline
- Retrying a Pipeline
- Passing Manual Review
- Obtaining Custom Parameters Required for Pipeline Running
- Rejecting Manual Review
- Querying Pipeline Logs
- Obtaining the Pipeline Step Execution Output
- Querying Build Products on a Pipeline
- Deleting Pipelines in Batches
- Disabling a Pipeline
- Setting Pipeline Tags in Batches
- Enabling a Pipeline
- Executing Pipelines in Batches
- Querying Pipeline Job Logs
- Passing a Delayed Execution Job
- Rejecting a Delayed Execution Job
- Delaying the Execution for One Hour
- Passing the Manual Check Point
- Rejecting the Manual Check Point
- Resuming a Pipeline
- Querying the Batch Pipeline Execution Result
- Switching Group Sequence
- Querying CodeArts Pipeline Notifications
- Updating CodeArts Pipeline notifications
- Enabling or Disabling CodeArts Pipeline Notifications
- Querying Third-Party Pipeline Notifications
- Updating Third-Party Pipeline Notifications
- Querying Pipeline Role Permissions
- Querying Pipeline User Permissions
- Modifying Pipeline Role Permissions
- Modifying Pipeline User Permissions
- Querying Whether Pipeline Resource-Level Permission Is Enabled
- Updating Pipeline Resource-Level Permissions Status
- Setting Pipeline Resource-Level Permissions for Different Roles
- Canceling a Pipeline Queuing
- Querying Queuing Records in the Current Pipeline
- Querying the Running Records of a Pipeline of the Old Version
- Querying Parameters Used in a Pipeline
- Rolling Back the Pipeline Execution
- Obtaining the Step Redirection Link
- Querying the Running Changes in a Pipeline
- Querying Available Predefined Parameters
- Querying Pipeline Triggering Failure Records
- Querying the Pipeline Editing History
- Creating a Parameter Group
- Editing a Parameter Group
- Deleting a Parameter Group
- Associating a Pipeline with a Parameter Group
- Querying Details About a Parameter Group
- Querying Parameter Groups Associated with a Pipeline
- Querying the Parameter Group List
- Obtaining Webhook Information
- Group Management
- Rule Management
- Tenant-Level Policy Management
- Project-Level Policy Management
-
Extension Management
- Creating an Extension Version
- Creating an Extension Draft Version
- Creating a Publisher
- Updating an Extension Draft
- Publishing an Extension Draft
- Updating Basic Information of an Extension
- Publishing an Extension
- Binding an Extension to a Publisher
- Updating the Extension Icon
- Updating the Publisher Icon
- Deleting an Extension Draft
- Querying the Publisher List
- Querying the Available Publisher
- Querying the Available Extension List
- Querying the Basic Extension List
- Querying the Available Extensions by Page
- Querying the Extension List
- Querying Extension Indicator Configuration
- Query Extension Input Configuration
- Query Extension Output Configuration
- Querying All Versions of an Extension
- Querying Extension Version Details
- Querying the Extension Version
- Deleting a Publisher
- Querying Publisher Details
- Creating a Basic Extension
- Updating a Basic Extension
- Deleting a Basic Extension
- Uploading a Basic Extension
- Querying the Basic Extension Details
- Endpoint Management
- Pipeline Tag Management
-
Change Management
- Create a Change
- Querying the Change Details
- Modifying the Change Status
- Modifying the Code Repository of a Change
- Querying the Change List
- Querying Changes in a Pipeline
- Querying Changes Being Released
- Querying the Change Operation History
- Querying Change Creator Information in a Project
- Querying Work Items Associated with a Change
- Updating Work Items Associated with a Change
- Microservice Management
- Template Management (Old Version, Unavailable Soon)
-
Pipeline Management (Old Version, Unavailable Soon)
- Quickly Creating a Pipeline and Jobs with a Template
- Checking the Pipeline Creation Status
- Starting a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Statuses in Batches
- Deleting a Pipeline
- Obtaining the Pipeline List
- Obtaining the Pipeline Status
- Obtaining the Pipeline Execution Status in a Project
- Application Examples
- Appendixes
- Change History
-
FAQs
- Functions
-
Troubleshooting
- Pipeline Fails to Run Because Repository Not Found
- Pipeline Fails to Run Because the Test Suite Is Already in Progress
- Pipeline Fails to Run Because Job Not Found
- Pipeline Is Not Triggered at a Specified Time
- Execution Button Is Unavailable
- Inappropriate Reviewer Configured for the Manual Review Job
- Subpipeline Not Found
- Change-triggered Pipeline Fails to Run and an Error Message Is Returned: "authentication required"
- Pipeline Fails to Run Because Deployment Policy Not Found
- Videos
- General Reference
Copied.
Querying the Running Changes in a Pipeline
Function
This API is used to query the running changes in a pipeline.
Calling Method
For details, see Calling APIs.
URI
GET /v5/{project_id}/api/pipelines/{pipeline_id}/pipeline-runs/{pipelineRunId}/query-change-requests
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
pipelineRunId |
Yes |
String |
Pipeline run |
project_id |
Yes |
String |
Parameter description: CodeArts project ID. Constraints: N/A. Value Range: The value contains 32 characters. Default value: N/A. |
pipeline_id |
Yes |
String |
Parameter description: Pipeline ID. Constraints: N/A. Value Range: The value contains 32 characters. Default value: N/A. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
component_id |
No |
String |
Microservice ID. |
Request Parameters
None
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
[items] |
Array of QueryPipelineRunChangeRequestsResp objects |
Response body. |
Parameter |
Type |
Description |
---|---|---|
id |
String |
Change ID. |
component_id |
String |
Microservice ID. |
status |
String |
Change status. |
title |
String |
Change title. |
creator_id |
String |
Change creator ID. |
creator_name |
String |
Change creator name. |
create_time |
String |
Change creation time. |
repos |
Array of strings |
Code repository associated with the change. |
Example Requests
GET https://(endpoint)/v5/e2e18230a85d4d6ab0b56cb6d2246c18/api/pipelines/771d3f5473404676872467e230289ebe/pipeline-runs/76711eae71644c38a235b77365d57845/query-change-requests?component_id=c1de96a98c084a0b8631f9e6ac8967b0
Example Responses
Status code: 200
Response body.
[ {
"id" : "211847a825754f2eadfa326c77fd4e9e",
"component_id" : "c1de96a98c084a0b8631f9e6ac8967b0",
"status" : "revoked",
"title" : "0328",
"creator_id" : "05d8ca972f114765a8984795a8aa4d41",
"creator_name" : "123",
"create_time" : "1711613423",
"repos" : [ ]
} ]
Status Codes
Status Code |
Description |
---|---|
200 |
Response body. |
Error Codes
See Error Codes.
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.
Chatbot