summaryrefslogtreecommitdiff
path: root/db
Commit message (Collapse)AuthorAgeFilesLines
* Re-organize queues to use for Sidekiqseparate-sidekiq-queuesYorick Peterse2016-10-211-0/+109
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370
* Merge branch 'fix_project_member_access_levels' into 'master' Sean McGivern2016-10-212-1/+16
|\ | | | | | | | | | | | | | | | | Fix project member access levels Migrate invalid project members (owner -> master) Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/18616 See merge request !6957
| * Fix project member access levelsfix_project_member_access_levelsValery Sizov2016-10-212-1/+16
| |
* | Fix broken label uniqueness label migrationStan Hu2016-10-211-2/+2
|/ | | | | | | | | | | | | | | | | The previous implementation of the migration failed on staging because the migration was attempted to remove labels from projects that did not actually have duplicates. This occurred because the SQL query did not account for the project ID when selecting the labels. To replicate the problem: 1. Disable the uniqueness validation in app/models/label.rb. 2. Create a duplicate label "bug" in project A. 3. Create the same label in project B with label "bug". The migration will attempt to remove the label in B even if there are no duplicates. Closes #23609
* Create project feature when project is createdissue_22944Felipe Artur2016-10-192-1/+29
|
* Split migration to create label prioritiesDouglas Barbosa Alexandre2016-10-194-32/+55
|
* Add label type to group and project labels listsDouglas Barbosa Alexandre2016-10-192-3/+34
|
* Add LabelPriority modelDouglas Barbosa Alexandre2016-10-192-2/+68
|
* Add column type to labels and do the batch update in the same migrationDouglas Barbosa Alexandre2016-10-192-18/+6
|
* Add ProjectLabel modelDouglas Barbosa Alexandre2016-10-191-0/+17
|
* Add GroupLabel modelDouglas Barbosa Alexandre2016-10-193-0/+26
|
* Merge remote-tracking branch 'origin/master' into 22191-delete-dynamic-envs-mr22191-delete-dynamic-envs-mrKamil Trzcinski2016-10-182-0/+15
|\
| * Add visibility level to project repositoryissue_19734_2Felipe Artur2016-10-172-1/+16
| |
* | Add on_stop column [ci skip]Kamil Trzcinski2016-10-172-22/+2
| |
* | Update `db/schema.rb`Kamil Trzcinski2016-10-171-1/+2
| |
* | Refactor code to use available and stopped statuses and refactor views to ↵Kamil Trzcinski2016-10-174-13/+33
| | | | | | | | use separate renders
* | Merge remote-tracking branch 'origin/master' into 22191-delete-dynamic-envs-mrKamil Trzcinski2016-10-173-564/+676
|\ \ | |/
| * Use activerecord_sane_schema_dumperRémy Coutable2016-10-121-587/+587
| | | | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
| * Precalculate trending projectsprecalculate-trending-projectsYorick Peterse2016-10-102-1/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces a Sidekiq worker that precalculates the list of trending projects on a daily basis. The resulting set is stored in a database table that is then queried by Project.trending. This setup means that Unicorn workers no longer _may_ have to calculate the list of trending projects. Furthermore it supports filtering without any complex caching mechanisms. The data in the "trending_projects" table is inserted in the same order as the project ranking. This means that getting the projects in the correct order is simply a matter of: SELECT projects.* FROM projects INNER JOIN trending_projects ON trending_projects.project_id = projects.id ORDER BY trending_projects.id ASC; Such a query will only take a few milliseconds at most (as measured on GitLab.com), opposed to a few seconds for the query used for calculating the project ranks. The migration in this commit does not require downtime and takes care of populating an initial list of trending projects.
| * Add markdown cache columns to the database, but don't use them yetNick Thomas2016-10-072-8/+66
| | | | | | | | | | | | | | | | | | | | | | | | This commit adds a number of _html columns and, with the exception of Note, starts updating them whenever the content of their partner fields changes. Note has a collision with the note_html attr_accessor; that will be fixed later A background worker for clearing these cache columns is also introduced - use `rake cache:clear` to set it off. You can clear the database or Redis caches separately by running `rake cache:clear:db` or `rake cache:clear:redis`, respectively.
* | Allow to close environmentsKamil Trzcinski2016-10-062-2/+4
| |
* | Make environments to be close ableKamil Trzcinski2016-10-061-2/+8
| |
* | Initial support for closing environmentsKamil Trzcinski2016-10-061-0/+9
|/
* Fix pipeline fixtures and calls to removed methodGrzegorz Bizon2016-10-041-1/+1
|
* Allow Member.add_user to handle access requestersRémy Coutable2016-09-281-1/+1
| | | | | | | | | | | | | | | | | | | | | Changes include: - Ensure Member.add_user is not called directly when not necessary - New GroupMember.add_users_to_group to have the same abstraction level as for Project - Refactor Member.add_user to take a source instead of an array of members - Fix Rubocop offenses - Always use Project#add_user instead of project.team.add_user - Factorize users addition as members in Member.add_users_to_source - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects - Destroy any requester before adding them as a member - Improve the way we handle access requesters in Member.add_user Instead of removing the requester and creating a new member, we now simply accepts their access request. This way, they will receive a "access request granted" email. - Fix error that was previously silently ignored - Stop raising when access level is invalid in Member, let Rails validation do their work Signed-off-by: Rémy Coutable <remy@rymai.me>
* Improvements to user organization field feature after code reviewDmitriy Zaporozhets2016-09-271-17/+0
| | | | | | | * Add newline to user organization spec according to test guide * Remove unnecessary comments from user organization database migration Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Add organization field to user profileDmitriy Zaporozhets2016-09-272-1/+31
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Merge branch 'fix/database-seeds' into 'master' Rémy Coutable2016-09-231-8/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix database seeds for development environment ## What does this MR do? This MR fixes database seeds for development environment and adds CI test for it. ## Why was this MR needed? Database seeds for development environment are often broken, and we are not able to catch that when someone modified `db/fixtures` and forgets to reseed database. Closes #22422 See merge request !6475
| * Limit test environment size to one project in CIGrzegorz Bizon2016-09-231-8/+3
| |
* | Add index on labels titleAhmad Sherif2016-09-232-1/+13
|/
* Update db/schema.rb per most recent migrationsupdate-db-schemaYorick Peterse2016-09-211-4/+5
| | | | | It seems this wasn't updated properly when migrations were added in a previous commit.
* Implement a second round of review comments from @DouweM.Timothy Andrew2016-09-211-1/+1
| | | | | | | | | | | | | | - Don't use `TableReferences` - using `.arel_table` is shorter! - Move some database-related code to `Gitlab::Database` - Remove the `MergeRequest#issues_closed` and `Issue#closed_by_merge_requests` associations. They were either shadowing or were too similar to existing methods. They are not being used anywhere, so it's better to remove them to reduce confusion. - Use Rails 3-style validations - Index for `MergeRequest::Metrics#first_deployed_to_production_at` - Only include `CycleAnalyticsHelpers::TestGeneration` for specs that need it. - Other minor refactorings.
* Update schema.rbTimothy Andrew2016-09-201-12/+12
|
* Fix `ON DELETE CASCADE` migrations.Timothy Andrew2016-09-203-4/+4
| | | | Incorrect syntax.
* Implement review comments from @yorickpeterseTimothy Andrew2016-09-204-9/+9
| | | | | | | | | | | | | | 1. Change multiple updates to a single `update_all` 2. Use cascading deletes 3. Extract an average function for the database median. 4. Move database median to `lib/gitlab/database` 5. Use `delete_all` instead of `destroy_all` 6. Minor refactoring
* Merge remote-tracking branch 'origin/master' into 21170-cycle-analyticsTimothy Andrew2016-09-2010-10/+111
|\
| * Merge branch 'master' into per-build-tokenKamil Trzcinski2016-09-195-5/+42
| |\
| | * Cleanup changesKamil Trzcinski2016-09-191-20/+0
| | |
| | * Added missing db/schema changesKamil Trzcinski2016-09-191-1/+2
| | |
| | * Add support for dynamic environmentsKamil Trzcinski2016-09-191-0/+29
| | | | | | | | | | | | Environments that can have a URL with predefined CI variables.
| | * Merge branch 'increase_artifact_size_column' into 'master' Yorick Peterse2016-09-162-2/+17
| | |\ | | | | | | | | | | | | | | | | Increase ci_builds artifacts_size column to 8-byte integer to allow larger files See merge request !6333
| | | * Increase ci_builds artifacts_size column to 8-byte integer to allow larger filesDrew Blessing2016-09-152-2/+17
| | | |
| | * | Merge branch 'group-specific-lfs-settings' into 'master' Rémy Coutable2016-09-162-0/+13
| | |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added group-specific setting for LFS. Groups can enable/disable LFS, but this setting can be overridden at the project level. **Admin only** Closes #18092 See merge request !6164
| | | * | Improved helper methods, better flow for `project.lfs_enabled?`, and UI fixes.Patricio Cano2016-09-151-17/+0
| | | | |
| | | * | Added group-specific setting for LFS.Patricio Cano2016-09-152-0/+30
| | | |/ | | | | | | | | | | | | Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
| | * | Fix undefined method when reverting migration RemoveProjectsPushesSinceGcfix/irreversible-migrationDouglas Barbosa Alexandre2016-09-151-1/+1
| | |/
| * | Merge remote-tracking branch 'origin/lfs-support-for-ssh' into per-build-tokenKamil Trzcinski2016-09-152-4/+11
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | # Conflicts: # app/controllers/projects/git_http_client_controller.rb # app/helpers/lfs_helper.rb # lib/gitlab/auth.rb # spec/requests/lfs_http_spec.rb
| | * | Refactor LFS token logic to use a Redis key instead of a DB field, making it ↵Patricio Cano2016-09-152-32/+0
| | | | | | | | | | | | | | | | a 1 use only token.
| | * | Added LFS support to SSHPatricio Cano2016-09-152-0/+32
| | |/ | | | | | | | | | - Required on the GitLab Rails side is mostly authentication and API related.
| | * Merge branch 'fix-old-migration-repos-path-key' into 'master' Robert Speicher2016-09-151-1/+4
| | |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update references to deprecated `repos_path` configuration key to avoid ## What does this MR do? Update references to deprecated `repos_path` configuration key to avoid errors when updating GitLab from older versions ## Why was this MR needed? Users were reporting errors when upgrading from GitLab 6.7 ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1464 See merge request !6350
View Lorry Controller Status