- 18 Jul, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 17 Jul, 2017 3 commits
-
-
Grzegorz Bizon authored
Simply re-raise an exception when it occurs, but guarantee that no background migration is lost in the process.
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
It also makes it possible to gracefully retry a migration in order to avoid problems like deadlocks.
-
- 14 Jul, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
We first pop a job from the Sidekiq queue / scheduled set and only if this has been successfully deleted we process the job. This makes it possible to minimize a possibility of a race condition happening.
-
- 13 Jul, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 11 Jul, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 12 Jun, 2017 1 commit
-
-
Yorick Peterse authored
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.
-