Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
a31b474e
Commit
a31b474e
authored
Feb 16, 2021
by
Grzegorz Bizon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Describe a proposal and add epics to ci_builds blueprint
parent
8da9785a
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
5 deletions
+23
-5
doc/architecture/blueprints/improve_ci_builds/index.md
doc/architecture/blueprints/improve_ci_builds/index.md
+23
-5
No files found.
doc/architecture/blueprints/improve_ci_builds/index.md
View file @
a31b474e
...
@@ -96,16 +96,31 @@ and the amount of queries executed using the table. This significantly hinders
...
@@ -96,16 +96,31 @@ and the amount of queries executed using the table. This significantly hinders
the development velocity and contributes to incidents on the production
the development velocity and contributes to incidents on the production
environment.
environment.
## Proposal
We want to start from migrating primary keys what is the most urgent thing. We
will need to create a new column and copy all the ids. It means that building
reliable and fast background migrations is a prerequisite for getting it done.
We will also need better background migrations to migrate data out of the
`ci_builds`
table and to setup partitioning for this table once we settle on
our partitioning strategy for it.
There are multiple ways to partition
`ci_builds`
table, but because the
importance and relevance of a pipeline data decays with time, we might want to
use a pipeline creation date as a partitioning key. Choosing the viable
strategy for partitioning this table is in the scope of this blueprint.
## Iterations
## Iterations
1.
Redesign background migrations to make them reliable
1.
[
Redesign background migrations to make them reliable
](
https://gitlab.com/groups/gitlab-org/-/epics/5415
)
1.
Migrate primary key of
`ci_builds`
table to 64-bit integer
1.
[
Migrate primary key of `ci_builds` table to 64-bit integer
](
https://gitlab.com/groups/gitlab-org/-/epics/5416
)
1.
Migrate eligible data out of the
`ci_builds`
table
1.
[
Migrate eligible data out of the `ci_builds` table
](
https://gitlab.com/groups/gitlab-org/-/epics/4685
)
1.
Devise a partitioning strategy for
`ci_builds`
table
1.
[
Devise a partitioning strategy for `ci_builds` table
](
https://gitlab.com/groups/gitlab-org/-/epics/5417
)
## Status
## Status
Blueprint in
progress
.
Blueprint in
approval
.
## Who
## Who
...
@@ -130,5 +145,8 @@ DRIs:
...
@@ -130,5 +145,8 @@ DRIs:
| Leadership | Darby Frey |
| Leadership | Darby Frey |
| Product | Jackie Porter |
| Product | Jackie Porter |
| Engineering | Grzegorz Bizon |
| Engineering | Grzegorz Bizon |
| Domain Expert / Verify | Fabio Pitino |
| Domain Expert / Database | Jose Finotto |
| Domain Expert / PostgreSQL | Nikolay Samokhvalov |
<!-- vale gitlab.Spelling = YES -->
<!-- vale gitlab.Spelling = YES -->
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment