Commit graph

12 commits

Author SHA1 Message Date
Pascal Borreli
12e3eff462 Fixed typos 2018-04-27 08:50:05 +00:00
Sean McGivern
3772310423 Add more detail to cleanup steps for background migrations
1. We can't just steal from the queue, in case there was a problem with Sidekiq.
2. We need to consider import / export.
2018-04-18 11:06:59 +01:00
Bob Van Landuyt
917fb1744c [docs] Info rescheduling background migrations 2018-02-08 09:44:59 +01:00
Ville Skyttä
0cbbb08e79 doc: Spelling fixes 2018-01-19 12:09:59 +02:00
Douwe Maan
1e6ca3c41e Consistently schedule Sidekiq jobs 2017-12-05 11:59:39 +01:00
Sean McGivern
989ccd7171 Document manual cleanup after background migration stealing 2017-09-25 12:48:07 +01:00
Yorick Peterse
ea2d0c4861
Update the update guides for background migrations
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.
2017-08-04 13:34:37 +02:00
Grzegorz Bizon
433b6fed29 Copy-edit background migrations guidelines 2017-07-21 13:19:35 +02:00
Grzegorz Bizon
367a895511 Extend background migration development guidelines 2017-07-20 13:46:13 +02:00
Grzegorz Bizon
4fa822ae9d Improve code examples in background migrations docs 2017-07-07 15:08:15 +02:00
Grzegorz Bizon
945cdf326e Make it possible to schedule bg migrations in bulk 2017-07-07 15:08:15 +02:00
Yorick Peterse
d83ee2bbd1
Add the ability to perform background migrations
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.
2017-06-12 13:24:04 +02:00