Tuesday 2023-10-10 14:50 UTC - `gitlab-org/gitlab` broken `master` with
gitlab-org/gitlab pipeline #1032139477 failed
Project | Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|---|
gitlab-org/gitlab | 1032139477 |
master |
Merge branch '390667-table-constraint-creates-a-new-index' into 'master' | Updates schema validation index query | push |
0.06 minutes | Prabakaran Murugesan |
Failed jobs (0):
General guidelines
Follow the Broken master
handbook guide.
Investigation
Please capture your investigation steps in the Investigation Steps
thread.
- If the failure is new, and looks like a potential flaky failure, you can retry the failing job and post a link to the retried job.
You can use the
retry_job
orretry_pipeline
commands by commenting on this incident with:
command | purpose |
---|---|
@gitlab-bot retry_job <job_id> |
Retry a failed job. Job ID must be associated with this incident. Every job can only be retried once. |
@gitlab-bot retry_pipeline <pipeline_id> |
Retry all failed jobs in a pipeline. Pipeline ID must be the one reported in this incident. |
- If the failure looks like a broken
master
, communicate the brokenmaster
in Slack using the "Broadcast Master Broken" workflow:
- Click the Shortcut lightning bolt icon in the
#master-broken
channel and select "Broadcast Master Broken". - Click "Continue the broadcast" after the automated message in
#master-broken
.
Root Cause Analysis
- It is important to categorize the incident by its root cause to identify corrective actions and to track data for furture references.
- Root cause labels can be found in the Broken
master
handbook guide. Search forPlease set the appropriate ~master-broken:* label from the list below
.
Pre-resolution
If you believe that there's an easy resolution by either:
- Reverting a particular merge request.
- Making a quick fix (for example, one line or a few similar simple changes in a few lines).
You can create a merge request, assign to any available maintainer, and ping people that were involved/related to the introduction of the failure.
Additionally, a message can be posted in
#backend_maintainers
or#frontend_maintainers
to get a maintainer take a look at the fix ASAP.
In both cases, make sure to add the pipeline:expedite label, and master:broken
or master:foss-broken
label, to speed up the master
-fixing pipelines.