Backend: Improve POST Trigger Pipeline API performance
Summary
Recently, to realign the pipeline process with teams that should own certain endpoints, the pipeline creation endpoint was moved over to grouppipeline authoring from a discussion in verify-stage#554 (closed) and the implementation in #457797 (closed) to adjust the feature_category values in the associated endpoints.
The endpoint list below was moved over to grouppipeline authoring.
RunPipelineScheduleWorker
PipelinesController#create
CreatePipelineWorker
Ci::ExternalPullRequests::CreatePipelineWorker
MergeRequests::CreatePipelineWorker
POST /trigger/pipeline
POST /pipeline
POST /merge_requests/:mr_id/pipelines
Proposal
The number 6 in the list is the largest of the new endpoint additions that negatively impact the overall grouppipeline authoring error budget.
See below:
The proposal is to investigate the root cause of the slowness and implement performance improvements to help bring PA error budget back to health
Confirm purpose and User Reception (how does this benefit the user?)
The pipeline creation process will also allow user pipelines to get to the execution part more quickly in the future. It will also help reduce the alerts of pipeline creation taking longer than 5 minutes in #g_pipeline-authoring_alerts.
Additional details
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Is this EE or CE?
-
EE -
CE
-
- Additional comments: