- 20 Sep, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 19 Sep, 2017 1 commit
-
-
Greg Stark authored
-
- 18 Sep, 2017 3 commits
-
-
Yorick Peterse authored
This removes the need for a default scope that adds a "WHERE project_id = X" clause. This commit also includes an additional index for Environment#last_deployment, ensuring this query uses just an index scan instead of also applying a Filter. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36877
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 15 Sep, 2017 1 commit
-
-
Felipe Artur authored
-
- 14 Sep, 2017 6 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
-
Yorick Peterse authored
This index is required to allow fast retrieval of recent push events without merge requests. Without this index in place the query would lead to PostgreSQL scanning over 150 000 index entries all the time, easily taking up between 200 and 500 milliseconds. This index reduces the time spent in this process to around 40 milliseconds on GitLab.com.
-
- 13 Sep, 2017 2 commits
-
-
Robert Speicher authored
This reverts merge request !14240
-
Yorick Peterse authored
-
- 12 Sep, 2017 1 commit
-
-
Robert Speicher authored
This file is a duplicate of a post-deploy migration and appears to have been left in by mistake. Looping through the Users table in a foreground migration would've been a bad idea. [ci skip]
-
- 11 Sep, 2017 2 commits
-
-
Annabel Dunstone Gray authored
This reverts merge request !14148
-
Yorick Peterse authored
This is required as otherwise newly created events will start with the wrong ID.
-
- 08 Sep, 2017 1 commit
-
-
Rubén Dávila authored
Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'" This reverts merge request !13619
-
- 07 Sep, 2017 3 commits
-
-
Jarka Kadlecova authored
-
Zeger-Jan van de Weg authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 06 Sep, 2017 10 commits
-
-
Kamil Trzcinski authored
-
Rubén Dávila authored
-
Jarka Kadlecova authored
-
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
-
Sean McGivern authored
-
Sean McGivern authored
-
Ashley Dumaine authored
-
Ashley Dumaine authored
-
Zeger-Jan van de Weg authored
-
- 05 Sep, 2017 9 commits
-
-
Kamil Trzcinski authored
-
Jarka Kadlecova authored
-
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
To avoid having to implement legacy code handling for the obsolete `verified_signature` attribute and to avoid any race conditions during the zero-downtime-deployment we do the following: 1. Destroy all records 2. Migration: Use add_column_with_default to add the new attribute and update the verification_status values on records created between 1. and 2. 3. Deploy the new code 4. Post migration: Destroy all records Like this we make sure that at no point there is a record with a `nil` value for the new `verification_status` attribute.
-
Alexis Reigel authored
-
Alexis Reigel authored
-