summaryrefslogtreecommitdiff
path: root/db
Commit message (Collapse)AuthorAgeFilesLines
* Add rule_type to approval_project_rulesLucas Charles2019-07-173-0/+36
| | | | | Adds migration to introduce non-regular rule_types to approval_project_rules
* Fix wrong pages access level defaultVladimir Shushlin2019-07-173-2/+42
| | | | | - Set access level in before_validation hook - Add post migration for updating existing project_features
* Migrate null values for users.private_profileAdam Hegyi2019-07-152-1/+34
| | | | | - Background migration for changing null values to false - Set false as default value for private_profile DB column
* Reorder fields in boards schema to match EEsh-reorder-boards-schema-dbStan Hu2019-07-151-2/+2
| | | | This eliminates conflicts between CE and EE db/schema.rb files.
* Reorder application settings in db/schema.rb to match EEsh-reorder-application-settingsStan Hu2019-07-141-44/+44
| | | | | This makes the CE and EE tables consistent and ensures changes in the schema for the CE version don't cause conflicts with EE.
* Merge branch 'id-clean-up-mr-assignees-migration' into 'master'Andreas Brandl2019-07-121-0/+20
|\ | | | | | | | | Add cleanup migration for MR's multiple assignees See merge request gitlab-org/gitlab-ce!30269
| * Add cleanup migration for MR's mutliple assigneesid-clean-up-mr-assignees-migrationIgor Drozdov2019-07-091-0/+20
| | | | | | | | | | | | | | The migration steals the remaining background jobs of populating MRs with assignees, executes them synchronously and then makes sure that all the assignees are migrated
* | Merge branch 'bvl-rename-routes-after-user-rename' into 'master'Jan Provaznik2019-07-121-0/+48
|\ \ | | | | | | | | | | | | Set the name of a user-namespace to the user name See merge request gitlab-org/gitlab-ce!23272
| * | Fix incorrect namespaces & route for user-routesBob Van Landuyt2019-07-091-0/+48
| |/ | | | | | | | | | | | | | | This fixes the `Namespace#name` and `Route#name` for all user namespaces and their personal projects in case they don't match the user name anymore. More info info in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23272
* | Upgrade to Rails 5.2upgrade-rails-5-2-ceHeinrich Lee Yu2019-07-121-2/+2
| | | | | | | | Updates changed method names and fixes spec failures
* | Add a rubocop for Rails.loggerMayra Cabrera2019-07-101-2/+2
| | | | | | | | | | | | Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
* | Rename Gitlab::Importers moduleRyan Cobb2019-07-096-6/+6
| | | | | | | | | | In order to avoid confusion between Gitlab::Importers module and other like named modules, this renamed it to Gitlab::DatabaseImporters.
* | Remove CommonMetricsImporter patchRyan Cobb2019-07-097-27/+6
| | | | | | | | | | | | Remove CommonMetricsImporter patch and change all references to CommonMetrics::Importer. Move specs into their appropriate folders. Also cleans up some common_metric importer namespacing.
* | Move importers to lib folderRyan Cobb2019-07-095-139/+8
| | | | | | | | | | This moves our metric importers into the lib folder. This will allow them to be autoloaded instead of having to explicitly require them.
* | Refactor common metrics importerRyan Cobb2019-07-095-105/+140
|/ | | | | | | This refactors common metrics importer for two reasons. 1. To create a new pattern that can be followed by future importers that will minimize dependency collision and 2. To allow EE to more easily extend dependencies.
* Merge branch 'ce-10283-notifications-for-ci-minutes-quota-limit-approaching' ↵James Lopez2019-07-052-0/+10
|\ | | | | | | | | | | | | into 'master' Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14328 See merge request gitlab-org/gitlab-ce!30003
| * Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14328ce-10283-notifications-for-ci-minutes-quota-limit-approachingRubén Dávila2019-07-052-0/+10
| |
* | Merge branch 'zj-remove-stale-feature-flag-keys' into 'master'Andreas Brandl2019-07-052-1/+49
|\ \ | | | | | | | | | | | | Remove unused Gitaly feature flags See merge request gitlab-org/gitlab-ce!30302
| * | Remove unused Gitaly feature flagsZeger-Jan van de Weg2019-07-042-1/+49
| | | | | | | | | | | | | | | | | | | | | When GitLab was migrating to Gitaly, feature flags were used. These are now out of use, and essentially a no-op. But they do make the output of chatops ugly and the feature table is selected in full by the application.
* | | Fix call to removed GitPushServicece-12464-remove-gitpushserviceMarkus Koller2019-07-041-5/+7
| |/ |/|
* | Allow asynchronous rebase operations to be monitoredNick Thomas2019-07-042-0/+10
| | | | | | | | | | | | | | | | | | This MR introduces tracking of the `rebase_jid` for merge requests. As with `merge_ongoing?`, `rebase_in_progress?` will now return true if a rebase is proceeding in sidekiq. After one release, we should remove the Gitaly-based lookup of rebases. It is much better to track this kind of thing via the database.
* | Add Grafana to Admin > Monitoring menu when enabledManeschi Romain2019-07-033-0/+38
|/
* Merge branch '44990-remove-old-i' into 'master'Nick Thomas2019-07-031-19/+0
|\ | | | | | | | | Remove old migration specs that violate FactoriesInMigrationSpecs See merge request gitlab-org/gitlab-ce!30280
| * Remove old migrations and specs44990-remove-old-iHeinrich Lee Yu2019-07-031-19/+0
| | | | | | | | | | This removes old migrations that violate the FactoriesinMigrationSpecs cop
* | Show upcoming status for releasesJason Goodman2019-07-033-1/+31
|/ | | | | | Add released_at field to releases API Add released_at column to releases table Return releases to the API sorted by released_at
* Add username to deploy tokensKrasimir Angelov2019-07-022-0/+10
| | | | | | | | | This new attribute is optional and used when set instead of the default format `gitlab+deploy-token-#{id}`. Empty usernames will be saved as null in the database. Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.
* Merge branch '63690-issue-trackers-title' into 'master'Dmitriy Zaporozhets2019-07-022-0/+15
|\ | | | | | | | | | | | | Use title and description fields for issue trackers Closes #63690 See merge request gitlab-org/gitlab-ce!30096
| * Use title and description fields for issue trackers63690-issue-trackers-titleJarka Košanová2019-07-022-0/+15
| | | | | | | | | | - instead of using properties - backward compatibility has to be kept for now
* | Bring the InitSchema migration up to standardNick Thomas2019-07-021-1/+11
| |
* | Squash old migrationsNick Thomas2019-07-02815-17821/+1844
| | | | | | | | Use the `squasher` gem to squash migrations older than the start of 2018
* | Add Migration for Strategies Column on operations_feature_flag_scopesJason Goodman2019-07-012-1/+19
| |
* | Merge branch 'db-fixtures' into 'master'Sean McGivern2019-07-011-2/+2
|\ \ | |/ |/| | | | | db.fixtures: use print instead of puts See merge request gitlab-org/gitlab-ce!30134
| * db.fixtures: use print instead of putseyjhbb@gmail.com2019-06-271-2/+2
| |
* | Merge branch 'add-clusters-to-deployment' into 'master'Lin Jen-Shin2019-07-013-1/+34
|\ \ | | | | | | | | | | | | Add clusters association to deployment See merge request gitlab-org/gitlab-ce!29960
| * | Add cluster_id to deployments table as an FKThong Kuah2019-06-273-1/+34
| |/ | | | | | | | | | | | | | | | | | | We nullify when cluster is deleted as we want to keep the deployment record around. Add cluster as an optional association We will have only cluster for deployments where the build deploys to a kubernetes cluster
* | Merge branch '3264-project-aliases-ce' into 'master'Bob Van Landuyt2019-06-282-0/+26
|\ \ | |/ |/| | | | | CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14108 See merge request gitlab-org/gitlab-ce!29604
| * Create project_aliases tablePatrick Bajao2019-06-262-0/+26
| |
* | Merge branch 'refactor/remove-sentry-from-app-settings' into 'master'Stan Hu2019-06-262-5/+39
|\ \ | | | | | | | | | | | | Remove Sentry settings from application settings See merge request gitlab-org/gitlab-ce!28447
| * | refactor(db): remove Sentry from application settings, disable_ddl_transactionRoger Meier2019-06-251-0/+2
| | |
| * | refactor(db): remove Sentry from application settingsRoger Meier2019-06-252-5/+1
| | |
| * | refactor: remove Sentry from application settingsRoger Meier2019-06-251-0/+36
| |/
* | Add two new ActiveRecord models62214-migrations-and-modelsMayra Cabrera2019-06-253-0/+53
|/ | | | | | | | - Namespace::Storagestatistics will persist root namespace statistics - Namespace::AggregationSchedule will save information when a new update to the namespace statistics needs to be scheduled Both tables use 'namespace_id' as primary key
* Revert "Revert to `id: :integer`"Peter Leitzen2019-06-252-3/+22
| | | | This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.
* Merge branch 'sh-recover-ee-schema-backport-migration-failure' into 'master'Rémy Coutable2019-06-251-0/+48
|\ | | | | | | | | | | | | Prevent EE backport migrations from running if CE is not migrated Closes #63612 See merge request gitlab-org/gitlab-ce!30002
| * Prevent EE backport migrations from running if CE is not migratedsh-recover-ee-schema-backport-migration-failureStan Hu2019-06-251-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a user upgraded to any GitLab 11.x EE version but switched back to CE, it's possible the state of the EE tables are not in the right state for the EE backport migration to work properly. In particular, there were three tables that had trouble: * epics * geo_event_log * vulnerability_feedback The EE backport migration would fail while trying to add foreign key constraints because a key didn't exist in the table. This happens because any EE migration that add or removed columns between v11.0.0 and v11.11.3 are not guaranteed to be applied in an CE installation. The EE backport schema does not individually backport these migrations. We now check if certain columns are present to determine whether the backport migration is in the proper state. CE users are required to upgrade to v11.11.3 EE if they ever installed EE previously before they can go back to v12.x CE. Tested via: ``` git checkout -f v11.0.0-ee bundle exec rake db:reset git checkout .; git checkout -f v11.11.3 bundle exec rake db:migrate git checkout .; git checkout -f v12.0.0 bundle exec rake db:migrate <failure happens> ```
* | Rename to time_tracking_limit_to_hours30355-use-hours-only-for-time-trackingHeinrich Lee Yu2019-06-252-4/+4
| | | | | | | | Changes migration and all other places the attribute is used
* | Limit time tracking values to hoursJon Kolb2019-06-252-0/+22
|/ | | | | Adds an instance setting to limit display of time tracking values to hours only
* Renew Let's Encrypt certificatesVladimir Shushlin2019-06-242-0/+26
| | | | | | | | Add index for pages domain ssl auto renewal Add PagesDomain.needs_ssl_renewal scope Add cron worker for ssl renewal Add worker for ssl renewal Add pages ssl renewal worker queues settings
* Merge branch 'sync-merge-ref-upon-mergeability-check' into 'master'Douwe Maan2019-06-242-1/+26
|\ | | | | | | | | Automatically update MR merge-ref along merge status See merge request gitlab-org/gitlab-ce!29569
| * Automatically update MR merge-ref along merge statusOswaldo Ferreira2019-06-202-1/+26
| | | | | | | | | | | | | | | | | | | | | | | | This couples the code that transitions the `MergeRequest#merge_status` and refs/merge-requests/:iid/merge ref update. In general, instead of directly telling `MergeToRefService` to update the merge ref, we should rely on `MergeabilityCheckService` to keep both the merge status and merge ref synced. Now, if the merge_status is `can_be_merged` it means the merge-ref is also updated to the latest. We've also updated the logic to be more systematic and less user-based.
View Lorry Controller Status