Labels
Prioritized labels 25
Drag to reorder prioritized labels and change their relative priority.
-
Category:ServerlessGitLab.orgAll issues and MRs related to the Serverless category within devops::configure. https://about.gitlab.com/direction/configure/serverless/
-
dockerfileGitLab.org / GitLab Docs DEPRECATEDRelated to the dockerfiles present in the gitlab-docs project
-
Category:Chaos EngineeringGitLab.orgIssues related to chaos engineering (part of ~devops:configure stage)
-
devopsconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)
-
Category:Infrastructure as CodeGitLab.orgAll issues and MRs related to the Infrastructure as Code category within devops::configure. https://about.gitlab.com/direction/configure
-
[deprecated] Accepting merge requestsGitLab.org[deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
-
Category:Cluster MonitoringGitLab.orgIssues belonging to the Monitor stage Health group for product category Cluster Monitoring
-
Category:Auto DevOpsGitLab.orgIssues for Auto DevOps, part of the Configure stage of the DevOps lifecycle
-
Category:Code QualityGitLab.orgAll issues and MRs related to the Code Quality category. See https://about.gitlab.com/direction/secure/static-analysis/code-quality/
-
Category:Container RegistryGitLab.orgCategory label - Features that apply to management container registries
-
groupconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use group::environments. Issues belonging to the Configure group of the Configure stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#configure-group
-
Category:Continuous IntegrationGitLab.orgAll issues and MRs related to the continuous integration category within devops:verify https://about.gitlab.com/direction/verify/continuous_integration
-
infrastructure configurationGitLab.orgIssues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
-
Category:Cluster Cost OptimizationGitLab.orgIssues related to the "cluster cost optimization" category of the configure stage. See &503
-
Category:Cloud Native InstallationGitLab.org
-
development guidelinesGitLab.orgChanges or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)
-
groupsource codeGitLab.orgIssues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group
-
grouprunner coreGitLab.orgIssues belonging to the Runner group of the Verify stage of the DevOps lifecycle.
-
Category:Kubernetes ManagementGitLab.orgRelating the `Kubernetes Management` category within the configure stage
Labels 3,627
-
master-brokendependency-upgradeGitLab.orgmaster-broken incident caused by dependency upgrades to Ruby version, Node version, gem versions, etc..
-
master-brokenexternal-dependency-unavailableGitLab.orgThis is to indicate master broken incidents caused by external dependency issues such as npm registry down, RubyGems.org down, etc.
-
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-brokeninfrastructureGitLab.orgmaster-broken incidents caused by various infrastructure issue such as network error, runner memory limit reached, etc.
-
This label represents a broken master pipeline caused by failing to pull docker image from the image registry.
-
This label describes a broken master scenario with the error "Gitlab is unable to handle this request due to load."
-
master-broken::infrastructuregitlab-outageGitLab.orgmaster broken incidents caused by a gitlab outage or service disruption. Retry is not recommended for such incident unless we are certain the issue is fixed.
-
When master pipeline incident occurs due to the runner having no disk space left.
-
master-brokenjob-timeoutGitLab.orgThis label is to identify master broken incidents caused by job timing out
-
master-brokenmissing-test-coverageGitLab.orgBroken master pipelines caused by bugs introduced to the repo due to missing test coverage
-
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-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