Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
master-brokenfork-repo-test-gapGitLab.orgmaster-broken incidents occurred in fork repos, main FOSS and JiHu, due to code changes to the Gitlab main repo that does not have any test coverage for running in a fork repo.
-
master-brokengitalyGitLab.orgThis label is for master broken incidents occured because gitaly is failed to setup. See example: gitlab-org/quality/engineering-productivity/master-broken-incidents#625
-
master-brokengitlab-com-overloadedGitLab.orgThis label describes a broken master scenario with the error "Gitlab is unable to handle this request due to load."
-
master-brokeninfrastructureGitLab.orgmaster-broken incidents caused by various infrastructure issue such as network error, runner memory limit reached, etc.
-
master-brokenjob-timeoutGitLab.orgThis label is to identify master broken incidents caused by job timing out
-
master-brokenmulti-version-db-upgradeGitLab.orgMaster broken incidents caused by db:migrate:multi-version-upgrade job, see example: gitlab-org/quality/engineering-productivity/master-broken-incidents#5982
-
master-brokenneed-merge-trainGitLab.orgmaster-broken incidents caused by merging two merge requests impacting the outcomes of the same spec, potentially resulted in delayed pipeline feedback, would have been avoided if merge train is enabled
-
master-brokenpipeline-skipped-before-mergeGitLab.orgmaster-broken incidents caused by MR being merged without running a new pipeline
-
master-brokenrunner-disk-fullGitLab.orgWhen master pipeline incident occurs due to the runner having no disk space left.
-
master-brokenstate leakGitLab.orgTest data state leaked through test cases. The same as ~"flaky-test::state leak" but it's considered broken because it's almost always happening. See https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html#state-leak
-
master-brokentest-selection-gapGitLab.orgmaster-broken incidents caused by gap in the test selection process, meaning the tests that would have caught the issue was mistakenly filtered out via MR pipeline test selection.
-
master-brokenundeterminedGitLab.orgThe cause of the failure is not straight forward and yet to be determined
-
master:needs-investigationGitLab.orgIssues that caused "broken master" and were addressed by quarantining, reverting, or temporary workarounds.
-
mattermostGitLab.orgUsed to notify Mattermost Support for technical issues with GitLab Mattermost and escalation by GitLab Support
-
maturitycompleteGitLab.orgThis item is part of the plan to get the associated category to the complete maturity level
-
maturitylovableGitLab.orgThis item is part of the plan to get the associated category to the lovable maturity level
-
maturityminimalGitLab.orgThis item is part of the plan to get the associated category to the minimal maturity level
-
maturityplannedGitLab.orgThis item is part of the plan to get the associated category to the planned maturity level
Prioritized