Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/lib/gitlab/background_migration
AgeCommit message (Collapse)Author
2018-05-01Use stages position column to track stage indexGrzegorz Bizon
2018-04-24Rename stage index column name to priority columnGrzegorz Bizon
2018-04-24Improve stages index migration code readabilityGrzegorz Bizon
2018-04-24Improve performance of stages index migration on PostgreSQLGrzegorz Bizon
2018-04-24Make stages index background migration more idempotentGrzegorz Bizon
2018-04-24Add background migration that migrates stages indicesGrzegorz Bizon
2018-04-06[Rails5] Update `type_cast_*_database` methodsblackst0ne
2018-04-05Merge branch 'jej/mattermost-notification-confidentiality-10-6' into ↵Douwe Maan
'security-10-6' [10.6] Prevent notes on confidential issues from being sent to chat See merge request gitlab/gitlabhq!2366 # Conflicts: # app/helpers/services_helper.rb
2018-03-29Do not use STI mechanisms when migrating pipeline stagesGrzegorz Bizon
2018-03-09Reschedule commits_count background migrationJan Provaznik
We still have >100K unmigrated MergeRequestDiffs which don't have commits_count set yet (see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/17567#note_61904891) This migration re-schedules the original background migration. To assure that records are not processed twice, records with commits_count set are skipped. Related to #41698 and !17567
2018-03-01Merge branch 'feature/move_oauth_modules_to_auth_dir_structure' into 'master'Douwe Maan
Moved o_auth/saml/ldap modules under gitlab/auth See merge request gitlab-org/gitlab-ce!17359
2018-02-28Moved o_auth/saml/ldap modules under gitlab/authHoratiu Eugen Vlad
2018-02-22Merge branch 'master' into 'backstage/gb/build-stages-catch-up-migration'Grzegorz Bizon
# Conflicts: # db/schema.rb
2018-02-21Use convenient Rails helperMichael Kozono
2018-02-20Explicitly reference redefined modelsMichael Kozono
And move UntrackedFile into PopulateUntrackedUploadsDependencies, and move its spec into its own file.
2018-02-17Remove codebase dependencies from a BG migrationMichael Kozono
Specifically, `PopulateUntrackedUploads` and its spec.
2018-02-16Use a helper to schedule pipeline stages migrationGrzegorz Bizon
2018-02-15Merge branch 'master' into 'backstage/gb/build-stages-catch-up-migration'Grzegorz Bizon
Conflicts: db/schema.rb
2018-02-15Recover from unique constraint violation in stages migrationGrzegorz Bizon
2018-02-14Migrate pipeline stages in batches instead of single rowGrzegorz Bizon
2018-02-14Avoid dropping tables in testMichael Kozono
And use :migration tag to use deletion strategy, and to avoid caching tables, and to lock into a particular schema. Attempting to fix intermittent spec errors `PG::UndefinedTable: ERROR: relation "public.untracked_files_for_uploads" does not exist`.
2018-02-12Fix orphan temp table untracked_files_for_uploadsMichael Kozono
2018-02-12Fix last batch size equals max batch size errorMichael Kozono
2018-02-09Merge branch 'master' into backstage/gb/build-stages-catch-up-migrationGrzegorz Bizon
* master: (1480 commits) Conflicts: db/schema.rb
2018-02-08Handle uniqueness on fork_network_member creationBob Van Landuyt
Since the migration might be queued already and be rescheduled when it fails on a uniqueness error, this should help clearing the background migration queue faster.
2018-02-01port of 594e6a0a625^..f74c90f68c6Micaël Bergeron
2018-01-31Enable RuboCop Style/RegexpLiteralTakuya Noguchi
2018-01-18Reduce UPDATEs for background column type changesYorick Peterse
Prior to this commit we would essentially update all rows in a table, even those where the source column (e.g. `issues.closed_at`) was NULL. This in turn could lead to statement timeouts when using the default batch size of 10 000 rows per job. To work around this we don't schedule jobs for rows where the source value is NULL. We also don't update rows where the source column is NULL (as an extra precaution) or the target column already has a non-NULL value. Using this approach it should be possible to update 10 000 rows in the "issues" table in about 7.5 - 8 seconds. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/42158
2018-01-12Introduce PredicateMemoization cop and fix offensesLin Jen-Shin
with StrongMemoize
2018-01-10Denormalize commits count for merge request diffsJan Provaznik
For each MR diff an extra 'SELECT COUNT()' is executed to get number of commits for the diff. Overall time to get counts for all MR diffs may be quite expensive. To speed up loading of MR info, information about number of commits is stored in a MR diff's extra column. Closes #38068
2018-01-06Fix rubocop offense in build stage migration classesGrzegorz Bizon
2018-01-06Do not attempt to migrate legacy pipeline stagesGrzegorz Bizon
2018-01-06Fix Rubocop offenses in build status migrations :cop:Grzegorz Bizon
2018-01-06Migrate a build stage completely in a background migrationGrzegorz Bizon
2018-01-04Merge branch 'mk-no-op-delete-conflicting-redirects' into 'master'Douwe Maan
Prevent excessive DB load due to faulty DeleteConflictingRedirectRoutes background migration See merge request gitlab-org/gitlab-ce!16205
2018-01-04Merge branch 'sh-validate-path-project-import' into 'master'Yorick Peterse
Avoid leaving a push event empty if payload cannot be created See merge request gitlab-org/gitlab-ce!16214
2018-01-04Merge branch 'change-issues-closed-at-background-migration' into 'master'Sean McGivern
Use a background migration for migrating issues.closed_at See merge request gitlab-org/gitlab-ce!16083
2018-01-04Avoid leaving a push event empty if payload cannot be createdStan Hu
If the payload cannot be created for some reason, we could be left with a nil push event payload, which causes Error 500s when viewing the dashboard. Guard against this error and log when it happens. Avoids problems seen in #38823
2018-01-03Make DeleteConflictingRedirectRoutes no-opMichael Kozono
Both the post-deploy and background migration.
2018-01-03Use a background migration for issues.closed_atYorick Peterse
In a previous attempt (rolled back in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16021) we tried to migrate `issues.closed_at` from timestamp to timestamptz using a regular migration. This has a bad impact on GitLab.com and as such was rolled back. This commit re-implements the original migrations using generic background migrations, allowing us to still migrate the data in a single release but without a negative impact on availability. To ensure the database schema is up to date the background migrations are performed inline in development and test environments. We also make sure to not migrate that that doesn't need migrating in the first place or has already been migrated.
2018-01-02Cache merged and closed events data in merge_request_metrics tableOswaldo Ferreira
2017-12-06Process normal paths in batch containing bad pathsMichael Kozono
2017-12-04Follow symlinksMichael Kozono
In particular, the Omnibus uploads directory is generally a symlink.
2017-12-02Handle race conditionMichael Kozono
2017-12-02Address Rubocop offensesMichael Kozono
2017-12-02Don’t quote `NOW()` for created_at columnMichael Kozono
To fix for MySQL.
2017-12-02RefactorMichael Kozono
2017-12-02Don’t recreate deleted uploadsMichael Kozono
2017-12-02Get rid of timestamps on untracked files tableMichael Kozono
`updated_at` is now unnecessary and `created_at` is less useful due to removing the tracked field.
2017-12-02Bulk insert uploadsMichael Kozono
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-22 06:12:20 +0300