Thursday 2022-11-24 23:19 UTC - `gitlab-org/gitlab` broken `improve-master-broken-incidents` with rspec:flaky-tests-report, webpack-dev-server, feature-flags-usage, haml-lint, generate-apollo-graphql-schema, static-verification-with-database, static-an...
gitlab-org/gitlab pipeline #704715694 failed
Branch: improve-master-broken-incidents
Commit: Merge branch 'improve-master-broken-incidents' into 'master'
Triggered by Rémy Coutable • Source: merge_request_event
• Duration: 4.16 minutes
Failed jobs (15):
- rspec:flaky-tests-report
- webpack-dev-server
- feature-flags-usage
- haml-lint
- generate-apollo-graphql-schema
- static-verification-with-database
- static-analysis as-if-foss 2/2
- static-analysis as-if-foss 1/2
- static-analysis 2/2
- static-analysis 1/2
- detect-tests
- setup-test-env
- compile-test-assets as-if-foss
- compile-test-assets
- compile-production-assets
General guidelines
Follow the Broken master
handbook guide.
Investigation
Be sure to fill the Timeline
for this incident.
- If the failure is new, and looks like a potential flaky failure, you can retry the failing job.
Make sure to mention the retry in the
Timeline
and leave a link to the retried job. - 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
.
- Click the Shortcut lightning bolt icon in the
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-master-fixing" label, and master:broken
or master:foss-broken
label, to speed up the master
-fixing pipelines.