- 05 Nov, 2017 1 commit
-
-
Shinya Maeda authored
-
- 03 Nov, 2017 1 commit
-
-
Shinya Maeda authored
-
- 02 Nov, 2017 2 commits
-
-
Sean McGivern authored
We already had this the other way around (merge_request_diffs.merge_request_id), but this is needed to gather only the most recent diffs for a set of merge requests.
-
Douwe Maan authored
-
- 24 Oct, 2017 1 commit
-
-
Bob Van Landuyt authored
In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12932 we freed up some names. But we were still renaming them.
-
- 07 Oct, 2017 4 commits
-
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
- 06 Oct, 2017 1 commit
-
-
Rubén Dávila authored
-
- 05 Oct, 2017 5 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
This migration can take a bit of time to complete and I don't want to delay the deployment process.
-
- 29 Sep, 2017 2 commits
-
-
Lin Jen-Shin (godfat) authored
-
Sean McGivern authored
The first attempt didn't migrate all rows on GitLab.com, due to a couple of issues: 1. Some rows in merge_request_diffs had truly huge numbers of commits and diffs serialised - one in particular had 26,000 commits! 2. The jobs were sometimes on Sidekiq hosts with frequent OOM errors, leading to the job being lost. The previous commit adds more logging, and a more robust insertion method. This commit reschedules the jobs, with a generous pause between each.
-
- 25 Sep, 2017 1 commit
-
-
Stan Hu authored
Missing parens prevented this migration from working in some cases. Closes #38246
-
- 23 Sep, 2017 1 commit
-
-
Stan Hu authored
`email_provider` by default is NULL, and if a user had not logged the value would remain NULL. Upgrading to GitLab 10.0 would lead to a PG::UniqueViolation because the post-deploy migration would attempt to reinsert the entry because the NULL comparison between `users.email_provider` and `user_synced_attributes_metadata.email_provider` would never match. Closes #38246
-
- 15 Sep, 2017 1 commit
-
-
Felipe Artur authored
-
- 14 Sep, 2017 5 commits
-
-
Michael Kozono authored
…to stay within our query timeout of 60s. Also reduce the job interval to keep the same overall migration time of ~3.3 days.
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-
- 07 Sep, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 06 Sep, 2017 2 commits
-
-
Yorick Peterse authored
This finishes the procedure for migrating events from the old format into the new format. Code no longer uses the old setup and the database tables used during the migration process are swapped, with the old table being dropped. While the database migration can be reversed this will 1) take a lot of time as data has to be coped around 2) won't restore data in the "events.data" column as we have no way of restoring this. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
-
Alexander Keramidas authored
-
- 05 Sep, 2017 6 commits
-
-
Alexis Reigel authored
as we destroy all gpg_signatures we don't need to downcase the email addresses anymore.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
This is faster for the deployment process, as the destroyed signatures will be re-generated on demand again, instead of updating them all on deploy.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
- 25 Aug, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 23 Aug, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 22 Aug, 2017 3 commits
-
-
Toon Claes authored
-
Toon Claes authored
There might be some projects where the namespace was removed, but the project wasn't. For these the projects still have a `namespace_id` set. So this adds a post-deploy migration remove all projects that are pending delete, and have a `namespace_id` that is non-existing.
-
Grzegorz Bizon authored
-