Skip to content

Add scalability infradev triage

Sean McGivern requested to merge add-scalability-infradev-triage into master

We do infradev triage monthly, on the 14th (arbitrary date; other monthly tasks happen on the 21st and 1st).

Because the issues to triage here are in the gitlab-org group, we have to run the gitlab-triage gem with different arguments, and so it's easiest to create another directory for policies for Scalability that relate to gitlab-org.

Dry run output locally (after removing the date condition):

Performing a dry run.

===============================
Triaging the `gitlab-org` group
===============================

---------------------------
Processing rules for issues
---------------------------

-------------------------------------------------
Gathering resources for rule: **Infradev review**
-------------------------------------------------
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/gitlab-org/issues?per_page=100&labels=team%3A%3AScalability%2Cinfradev&state=opened
[DEBUG] rate_limit_infos: Rate limit remaining: 0 (reset at 1970-01-01 01:00:00 +0100)
[DEBUG] Rate limit almost exceeded, sleeping for -1609855526.180768 seconds


* Found 5 resources...
* Filtering resources...
* Total after filtering: 5 resources
* Limiting resources...
* Total after limiting: 5 resources

The following issue would be created in project `gitlab-com/gl-infra/scalability` for the rule **Infradev review**:

>>>
* Title: 2021-01-05 - infradev review
* Description: These issues in gitlab-org have [~"team::Scalability" and
~infradev][issue-list]. Please make sure that issues are
due to be resolved according to their [severity labels],
and help the relevant stage group if they need it. For
more information, see the [handbook page on the infradev
process][infradev]

- [ ] [Query for optimization and review the frequency of execution](https://gitlab.com/gitlab-org/gitlab/-/issues/292047) ~"Category:Continuous Integration", ~"backend", ~"candidate::13.8", ~"database", ~"devops::verify", ~"gitlab.com", ~"group::continuous integration", ~"infradev", ~"performance", ~"section::ops", ~"severity::1", ~"team::Scalability", ~"workflow::ready for development"
- [ ] [Add application limits for Jira imports](https://gitlab.com/gitlab-org/gitlab/-/issues/244859) ~"Application Limits", ~"Category:Jira Importer", ~"devops::plan", ~"group::project management", ~"infradev", ~"priority::3", ~"redis", ~"section::dev", ~"severity::3", ~"team::Scalability"
- [ ] [We cache rendered commit messages in Redis twice](https://gitlab.com/gitlab-org/gitlab/-/issues/244851) ~"Accepting merge requests", ~"Category:Source Code Management", ~"banzai", ~"bug", ~"devops::create", ~"group::source code", ~"infradev", ~"markdown", ~"performance", ~"priority::3", ~"redis", ~"section::dev", ~"severity::3", ~"team::Scalability"
- [ ] [Big sorted sets in redis for Elastic bookkeeping](https://gitlab.com/gitlab-org/gitlab/-/issues/244865) ~"Accepting merge requests", ~"Category:Global Search", ~"availability", ~"bug", ~"devops::enablement", ~"group::global search", ~"infradev", ~"performance", ~"priority::3", ~"section::enablement", ~"severity::3", ~"team::Scalability"
- [ ] [Create specialized worker for refreshing project authorizations during group deletion](https://gitlab.com/gitlab-org/gitlab/-/issues/223853) ~"backend", ~"backstage [DEPRECATED]", ~"devops::manage", ~"group::access", ~"infradev", ~"performance", ~"priority::2", ~"quad-planning::complete-no-action", ~"section::dev", ~"severity::2", ~"team::Scalability", ~"workflow::in review"

[issue-list]: https://gitlab.com/groups/gitlab-org/-/issues?label_name%5B%5D=team%3A%3AScalability&label_name%5B%5D=infradev
[infradev]: https://about.gitlab.com/handbook/engineering/workflow/#infradev
[severity labels]: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
/assign @smcgivern
/due 2021-01-12
/label ~"team::Scalability" ~"team-tasks"
>>>

Which would create an issue with this description:

Merge request reports