Update project management sharding key issues

changed milestone to %17.9

added Category:Team Planning Technical Roadmap database devopsplan groupproject management maintenancescalability sectiondev typemaintenance workflowin dev labels

assigned to @mcelicalderonG

added pipelinetier-1 label

added databasereview pending label

1 Message

CHANGELOG missing:

If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog.

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
database	`@morefice` (UTC+1, 6 hours ahead of author)	`@a_akgun` (UTC+3, 8 hours ahead of author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

Just a small change in table docs, pointing to a different sharding issue for each table, all in the Set sharding keys for tables in 'group::project... (&16534) epic

@ahegyi since it's such a small change, could you please review and set MWPS? I think you can give all the required approvals

requested review from @ahegyi

mentioned in epic gitlab-org#16534

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

You are the last maintainer of this merge request
The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

removed database label

added database databaseapproved labels and removed databasereview pending label

enabled automatic add to merge train when checks pass

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-cng: test report for 2b439a26

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Create      | 143    | 0      | 19      | 0     | 162   | ✅     |
| Package     | 30     | 0      | 14      | 0     | 44    | ✅     |
| Verify      | 51     | 0      | 19      | 0     | 70    | ✅     |
| Plan        | 86     | 0      | 8       | 0     | 94    | ✅     |
| Govern      | 84     | 0      | 10      | 0     | 94    | ✅     |
| Secure      | 2      | 0      | 5       | 0     | 7     | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 447    | 0      | 122     | 0     | 569   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-test-on-gdk: test report for 2b439a26

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Plan        | 82     | 0      | 8       | 0     | 90    | ✅     |
| Create      | 138    | 0      | 20      | 0     | 158   | ✅     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Verify      | 50     | 0      | 20      | 0     | 70    | ✅     |
| Govern      | 79     | 0      | 13      | 0     | 92    | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Package     | 25     | 0      | 13      | 0     | 38    | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Secure      | 4      | 0      | 3       | 0     | 7     | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 429    | 0      | 124     | 0     | 553   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

Hey there , could you please make sure this merge request gets merged?

The merge request is set to auto-merge, but it is not currently mergeable (MR detailed_merge_status is discussions_not_resolved).

This message was generated automatically. Improve it or delete it.

resolved all threads

started a merge train

removed this merge request from the merge train because the pipeline did not succeed. Learn more.

enabled automatic add to merge train when checks pass

started a merge train

merged

Hello @mcelicalderonG

The database team is looking for ways to improve the database review process and we would love your help!

If you'd be open to someone on the database team reaching out to you for a chat, or if you'd like to leave some feedback asynchronously, just post a reply to this comment mentioning: