The commit API failed to update pipeline status of a commit
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Title: API Failure to Update Existing Pipeline Status Under Version 16.11
Description:
Our company uses a self-hosted GitLab Premium instance 16.11.
Under GitLab version 16.11, my company encountered an issue with the Set the pipeline status of a commit API. Instead of updating the existing pipeline status, the API created an additional job within the pipeline, despite specifying the pipeline ID.
Steps to Reproduce:
Use the API endpoint Title: API Failure to Update Existing Pipeline Status Under Version 16.11
Description:
Under GitLab version 16.11, I encountered an issue with the Set the pipeline status of a commit API. Instead of updating the existing pipeline status, the API created an additional job within the pipeline, despite specifying the pipeline ID.
Steps to Reproduce:
Use the API endpoint https://gitlab.xxxxx.com/api/v4/projects/7888/statuses/6128486d0e3284870a90d73a553dc57ad2b03def to update the status of an existing pipeline.
And the paramters are
{
"state": "success",
"pipeline_id": 2204923
}Observe that a new job is created instead of updating the existing pipeline status.
Expected Behavior:
The API should update the status of the specified existing pipeline without creating additional jobs.
Actual Behavior:
The API creates a new job in the specified pipeline instead of updating its status.
Environment:
GitLab Version: 16.11 API Endpoint: POST /projects/:id/statuses/:sha Additional Information:
Please investigate this issue, as it affects the workflow by introducing unexpected jobs in pipelines.