summaryrefslogtreecommitdiff
path: root/db
Commit message (Collapse)AuthorAgeFilesLines
* Denormalize commits count for merge request diffs38068-commits-countJan Provaznik2018-01-102-1/+31
| | | | | | | | | For each MR diff an extra 'SELECT COUNT()' is executed to get number of commits for the diff. Overall time to get counts for all MR diffs may be quite expensive. To speed up loading of MR info, information about number of commits is stored in a MR diff's extra column. Closes #38068
* Merge branch 'jej/backport-authorized-keys-to-ce' into 'master'Douwe Maan2018-01-093-0/+37
|\ | | | | | | | | | | | | Backport authorized_keys Closes gitlab-ee#3953 See merge request gitlab-org/gitlab-ce!16014
| * Avoid adding index if already existsPaco Guzman2018-01-081-1/+2
| |
| * Backport authorized_keys_enabled defaults to true'Michael Kozono2018-01-082-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally from branch 'fix-authorized-keys-enabled-default-2738' via merge request https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2240 Removed background migrations which were intended to fix state after using Gitlab without a default having been set Squashed commits: Locally, if Spring was not restarted, `current_application_settings` was still cached, which prevented the migration from editing the file. This will also ensure that any app server somehow hitting old cache data will properly default this setting regardless. Retroactively fix migration This allows us to identify customers who ran the broken migration. Their `authorized_keys_enabled` column does not have a default at this point. We will fix the column after we fix the `authorized_keys` file. Fix authorized_keys file if needed Add default to authorized_keys_enabled setting Reminder: The original migration was fixed retroactively a few commits ago, so people who did not ever run GitLab 9.3.0 already have a column that defaults to true and disallows nulls. I have tested on PostgreSQL and MySQL that it is safe to run this migration regardless. Affected customers who did run 9.3.0 are the ones who need this migration to fix the authorized_keys_enabled column. The reason for the retroactive fix plus this migration is that it allows us to run a migration in between to fix the authorized_keys file only for those who ran 9.3.0. Tweaks to address feedback Extract work into background migration Move batch-add-logic to background migration Do the work synchronously to avoid multiple workers attempting to add batches of keys at the same time. Also, make the delete portion wait until after adding is done. Do read and delete work in background migration Fix Rubocop offenses Add changelog entry Inform the user of actions taken or not taken Prevent unnecessary `select`s and `remove_key`s Add logs for action taken Fix optimization Reuse `Gitlab::ShellAdapter` Guarantee the earliest key Fix migration spec for MySQL
| * Backport option to disable writing to `authorized_keys` fileMichael Kozono2018-01-082-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally branch 'mk-toggle-writing-to-auth-keys-1631' See merge request !2004 Squashed commits: Add authorized_keys_enabled to Application Settings Ensure default settings are exposed in UI Without this change, `authorized_keys_enabled` is unchecked when it is nil, even if it should be checked by default. Add “Speed up SSH operations” documentation Clarify the reasons for disabling writes Add "How to go back" section Tweak copy Update Application Setting screenshot
| * Backport authorized_keys branch 'find-key-by-fingerprint'Pablo Carranza2018-01-081-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add find key by base64 key or fingerprint to the internal API See merge request !250 Squashed changes: Add unique index to fingerprint Add new index to schema Add internal api to get ssh key by fingerprint Change API endpoint to authorized_keys Add InsecureKeyFingerprint that calculates the fingerprint without shelling out Add require for gitlab key fingerprint Remove uniqueness of fingerprint index Remove unique option from migration Fix spec style in fingerprint test Fix rubocop complain Extract insecure key fingerprint to separate file Change migration to support building index concurrently Remove those hideous tabs
* | Merge branch 'osw-merge-request-metrics-population-scheduler-improvement' ↵Stan Hu2018-01-081-31/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | into 'master' Remove unnecessary queries on Merge Request Metrics population scheduler Closes gitlab-org/release/tasks#13 See merge request gitlab-org/gitlab-ce!16292
| * | Remove unnecessary queries on Merge Request Metrics population schedulerOswaldo Ferreira2018-01-081-31/+1
| | |
* | | Add memoization for properties40418-migrate-existing-data-from-kubernetesservice-to-clusters-platforms-kubernetesShinya Maeda2018-01-081-4/+10
| | |
* | | Disable STI of ActiveRecord. Refactoring specs.Shinya Maeda2018-01-081-2/+20
| | |
* | | Fix StaticSnalysysShinya Maeda2018-01-081-1/+1
| | |
* | | Revert bulk_insert and bring back AR insert(one by one)Shinya Maeda2018-01-081-52/+26
| | |
* | | Use batch update for Service deactivationShinya Maeda2018-01-081-4/+5
| | |
* | | Fix query to look for proper unmanaged kubernetes serviceShinya Maeda2018-01-081-17/+12
| | |
* | | Fix static anylysyShinya Maeda2018-01-081-2/+3
| | |
* | | Use bulk_insert instead of AR createShinya Maeda2018-01-081-12/+45
| | |
* | | Opitmize migration process by using both unmanaged_kubernetes_service and ↵Shinya Maeda2018-01-081-34/+36
| | | | | | | | | | | | kubernetes_service_without_template
* | | Avoid quotes in ActiveRecord queryShinya Maeda2018-01-081-4/+4
| | |
* | | Use explicit namespace for avoiding reference from application codeShinya Maeda2018-01-081-13/+16
| | |
* | | Add logic to swtich environment_scope by the situationShinya Maeda2018-01-081-23/+29
| | |
* | | Add env_scope testsShinya Maeda2018-01-081-0/+1
| | |
* | | Fix commentsShinya Maeda2018-01-081-10/+10
| | |
* | | Fix migration file typos and reorder Table definitionShinya Maeda2018-01-081-25/+21
| | |
* | | Fix unmanaged_kubernetes_service scope for multiple clustersShinya Maeda2018-01-081-17/+27
| | |
* | | Add test. Disable KubernetesService when migratedShinya Maeda2018-01-081-11/+12
| | |
* | | Migrate existing data from KubernetesService to Clusters::Platforms::KubernetesShinya Maeda2018-01-081-0/+104
|/ /
* | Merge branch '41249-clearing-the-cache' into 'master'Kamil Trzciński2018-01-062-0/+14
|\ \ | | | | | | | | | | | | | | | | | | Resolve "Clearing the cache" Closes #41249 See merge request gitlab-org/gitlab-ce!16067
| * \ Merge branch 'master' into 41249-clearing-the-cacheMatija Čupić2018-01-053-2/+10
| |\ \ | | |/
| * | Fix jobs_cache_index migration class nameMatija Čupić2018-01-051-1/+1
| | |
| * | Merge branch 'master' into 41249-clearing-the-cacheMatija Čupić2018-01-0411-35/+294
| |\ \
| * | | Rename Project#cache_index to jobs_cache_indexMatija Čupić2018-01-042-2/+2
| | | |
| * | | Remove default value from cache_index migrationMatija Čupić2017-12-222-9/+3
| | | |
| * | | Add cache_index migrationMatija Čupić2017-12-222-1/+21
| | | |
* | | | Merge branch 'fix-ce-migration-timestamp' into 'master'Robert Speicher2018-01-063-7/+37
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Fix rebase commit SHA migration name See merge request gitlab-org/gitlab-ce!16256
| * | | | Add the EE `rebase_commit_sha` migration back in its original locationRobert Speicher2018-01-051-0/+22
| | | | |
| * | | | Fix rebase commit SHA migration namefix-ce-migration-timestampSean McGivern2018-01-052-7/+15
| | |_|/ | |/| | | | | | | | | | | | | | This already existed in EE with a different timestamp, so rename for CE and make it idempotent.
* | | | Merge branch 'sh-reuse-disk-repositories-seeder' into 'master'Stan Hu2018-01-051-1/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Skip project repository disk validation in development project seeder Closes gitlab-development-kit#310 See merge request gitlab-org/gitlab-ce!16257
| * | | | Skip project repository disk validation in development project seedersh-reuse-disk-repositories-seederStan Hu2018-01-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When seeding the GDK with new projects, it's very common to reuse the same repository names on disk. Previously, the validation would fail and leave the projects in a half-broken state. We can skip the validation to avoid causing odd errors. Closes gitlab-org/gitlab-development-kit#310
* | | | | Remove labeled issues seedremove_labeled_issues_seedFelipe Artur2018-01-051-112/+0
|/ / / /
* | | | Merge branch 'issue_40500' into 'master'Sean McGivern2018-01-051-0/+112
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | Improve filtering issues by label performance Closes #40500 and #37143 See merge request gitlab-org/gitlab-ce!16136
| * | | Improve filtering issues by label performanceissue_40500Felipe Artur2018-01-051-0/+112
| | | |
* | | | Backport 'Rebase' feature from EE to CEjprovazn-rebaseJan Provaznik2018-01-052-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a project uses fast-forward merging strategy user has to rebase MRs to target branch before it can be merged. Now user can do rebase in UI by clicking 'Rebase' button instead of doing rebase locally. This feature was already present in EE, this is only backport of the feature to CE. Couple of changes: * removed rebase license check * renamed migration (changed timestamp) Closes #40301
* | | | Ignore the Migration/Datetime cop in a migration that fix a column type to ↵Rémy Coutable2018-01-041-1/+1
| |_|/ |/| | | | | | | | | | | | | | datetime_with_timezone Signed-off-by: Rémy Coutable <remy@rymai.me>
* | | Merge branch 'mdelaossa/gitlab-ce-31995-project-limit-default-fix'Dmitriy Zaporozhets2018-01-042-2/+40
|\ \ \ | | | | | | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
| * | | User#projects_limit remove DB default and added NOT NULL constraintMario de la Ossa2017-12-302-2/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is required because otherwise if a user is created with a value for `projects_limit` that matches the DB default, it gets overwritten by `current_application_settings.default_projects_limit`. By removing the default we once again can allow a user to be created with a limit of 10 projects without the risk that it'll change to 10000
* | | | Merge branch 'mk-no-op-delete-conflicting-redirects' into 'master'Douwe Maan2018-01-041-26/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Prevent excessive DB load due to faulty DeleteConflictingRedirectRoutes background migration See merge request gitlab-org/gitlab-ce!16205
| * | | | Make DeleteConflictingRedirectRoutes no-opmk-no-op-delete-conflicting-redirectsMichael Kozono2018-01-031-26/+2
| | | | | | | | | | | | | | | | | | | | Both the post-deploy and background migration.
* | | | | Merge branch 'change-issues-closed-at-background-migration' into 'master'Sean McGivern2018-01-042-1/+46
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Use a background migration for migrating issues.closed_at See merge request gitlab-org/gitlab-ce!16083
| * | | | | Use a background migration for issues.closed_atchange-issues-closed-at-background-migrationYorick Peterse2018-01-032-1/+46
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In a previous attempt (rolled back in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16021) we tried to migrate `issues.closed_at` from timestamp to timestamptz using a regular migration. This has a bad impact on GitLab.com and as such was rolled back. This commit re-implements the original migrations using generic background migrations, allowing us to still migrate the data in a single release but without a negative impact on availability. To ensure the database schema is up to date the background migrations are performed inline in development and test environments. We also make sure to not migrate that that doesn't need migrating in the first place or has already been migrated.
* | | | | Cache merged and closed events data in merge_request_metrics tableOswaldo Ferreira2018-01-023-0/+110
|/ / / /
View Lorry Controller Status