Skip to content

Partition ci_pipelines_config table

Marius Bobin requested to merge 469056-partition-ci_pipelines_config into master

What does this MR do and why?

ci_pipelines_config is supposed to store the pipeline configuration YAML for debugging purposes, but we don't use it(don't even show it to the users), the information is not relevant because it's the config before the expansion and it's also taking up valuable disk space.

Sample of entries:

gitlabhq_development_ci=# select * from ci_pipelines_config limit 1;
 pipeline_id |          content          | partition_id
-------------+---------------------------+--------------
       10174 | ---                      +|          100
             | include:                 +|
             | - local: ".gitlab-ci.yml"+|
             |                           |
(1 row)

Here we're recreating the table as a partitioned table to match the other CI tables.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #469056 (closed)

Edited by Marius Bobin

Merge request reports