summaryrefslogtreecommitdiff
path: root/doc/development/background_migrations.md
Commit message (Collapse)AuthorAgeFilesLines
* [docs] Info rescheduling background migrationsbvl-fix-concurrent-fork-network-migrationsBob Van Landuyt2018-02-081-0/+12
|
* doc: Spelling fixesVille Skyttä2018-01-191-1/+1
|
* Consistently schedule Sidekiq jobsdm-application-workerDouwe Maan2017-12-051-5/+5
|
* Document manual cleanup after background migration stealingdocument-background-migration-stealingSean McGivern2017-09-251-1/+28
|
* Update the update guides for background migrationsYorick Peterse2017-08-041-0/+9
| | | | | | | | The introduction of background migrations means some of our requirements for online upgrades have to be adjusted / clarified. See https://gitlab.com/gitlab-org/gitlab-ce/issues/35939 for more information.
* Copy-edit background migrations guidelinesGrzegorz Bizon2017-07-211-7/+13
|
* Extend background migration development guidelinesGrzegorz Bizon2017-07-201-0/+30
|
* Improve code examples in background migrations docsGrzegorz Bizon2017-07-071-4/+2
|
* Make it possible to schedule bg migrations in bulkGrzegorz Bizon2017-07-071-4/+15
|
* Add the ability to perform background migrationsYorick Peterse2017-06-121-0/+205
Background migrations can be used to perform long running data migrations without these blocking a deployment procedure. See MR https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11854 for more information.