summaryrefslogtreecommitdiff
path: root/db/schema.rb
Commit message (Collapse)AuthorAgeFilesLines
* Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14597ce-docker_image_replication-event-generationValery Sizov2019-07-241-0/+9
| | | | | This is the first part of Docker Registry replication for secondary Geo node.
* Remove PostgreSQL opclasses monkey patchsh-remove-opclasses-patchStan Hu2019-07-231-662/+662
| | | | | | | | | | | This is no longer needed with Rails 5.2. opclass is the attribute used per https://github.com/rails/rails/pull/19090/files. Now that we've removed the monkey patch and restored the Rails schema dumper, it appears Rails has dropped the inclusion of `using: :btree` as well (https://github.com/rails/rails/pull/27981). Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64529
* Add index for issues on relative position, projectbw-add-index-for-relative-positionBrett Walker2019-07-221-0/+1
| | | | and state
* Apply changes recomended by merge request coachFabio Papa2019-07-191-1/+1
|
* Update schemaFabio Papa2019-07-191-0/+1
|
* Add rule_type to approval_project_rulesLucas Charles2019-07-171-0/+2
| | | | | Adds migration to introduce non-regular rule_types to approval_project_rules
* Fix wrong pages access level defaultVladimir Shushlin2019-07-171-2/+2
| | | | | - Set access level in before_validation hook - Add post migration for updating existing project_features
* Migrate null values for users.private_profileAdam Hegyi2019-07-151-1/+1
| | | | | - 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.
* Upgrade to Rails 5.2upgrade-rails-5-2-ceHeinrich Lee Yu2019-07-121-2/+2
| | | | Updates changed method names and fixes spec failures
* Merge branch 'ce-10283-notifications-for-ci-minutes-quota-limit-approaching' ↵James Lopez2019-07-051-0/+1
|\ | | | | | | | | | | | | 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-051-0/+1
| |
* | Merge branch 'zj-remove-stale-feature-flag-keys' into 'master'Andreas Brandl2019-07-051-1/+1
|\ \ | |/ |/| | | | | Remove unused Gitaly feature flags See merge request gitlab-org/gitlab-ce!30302
| * Remove unused Gitaly feature flagsZeger-Jan van de Weg2019-07-041-1/+1
| | | | | | | | | | | | | | 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.
* | Allow asynchronous rebase operations to be monitoredNick Thomas2019-07-041-0/+1
| | | | | | | | | | | | | | | | | | 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-031-0/+2
|/
* Show upcoming status for releasesJason Goodman2019-07-031-1/+2
| | | | | | 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-021-0/+1
| | | | | | | | | 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-021-0/+1
|\ | | | | | | | | | | | | 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-021-0/+1
| | | | | | | | | | - instead of using properties - backward compatibility has to be kept for now
* | Add Migration for Strategies Column on operations_feature_flag_scopesJason Goodman2019-07-011-1/+2
|/
* Merge branch 'add-clusters-to-deployment' into 'master'Lin Jen-Shin2019-07-011-1/+4
|\ | | | | | | | | Add clusters association to deployment See merge request gitlab-org/gitlab-ce!29960
| * Add cluster_id to deployments table as an FKThong Kuah2019-06-271-1/+4
| | | | | | | | | | | | | | | | | | | | 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-281-0/+10
|\ \ | |/ |/| | | | | 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-261-0/+10
| |
* | Merge branch 'refactor/remove-sentry-from-app-settings' into 'master'Stan Hu2019-06-261-5/+1
|\ \ | | | | | | | | | | | | Remove Sentry settings from application settings See merge request gitlab-org/gitlab-ce!28447
| * | refactor(db): remove Sentry from application settingsRoger Meier2019-06-251-5/+1
| |/
* | Add two new ActiveRecord models62214-migrations-and-modelsMayra Cabrera2019-06-251-0/+17
|/ | | | | | | | - 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-251-3/+3
| | | | This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.
* Rename to time_tracking_limit_to_hours30355-use-hours-only-for-time-trackingHeinrich Lee Yu2019-06-251-1/+1
| | | | Changes migration and all other places the attribute is used
* Limit time tracking values to hoursJon Kolb2019-06-251-0/+1
| | | | | Adds an instance setting to limit display of time tracking values to hours only
* Renew Let's Encrypt certificatesVladimir Shushlin2019-06-241-0/+1
| | | | | | | | 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-241-1/+1
|\ | | | | | | | | 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-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Don't show private keys for letsencrypt certsVladimir Shushlin2019-06-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds enum certificate_source to pages_domains table with default manually_uploaded Mark certificates as 'gitlab_provided' if the were obtained through Let's Encrypt Mark certificates as 'user_provided' if they were uploaded through controller or api Only show private key in domain edit form if it is 'user_provided' Only show LetsEncrypt option if is enabled by application settings (and feature flag) Refactor and fix some specs to match new logic Don't show Let's Encrypt certificates as well
* | Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into ↵Arun Kumar Mohan2019-06-201-4/+3
|\ \ | |/ | | | | db/update-geo-nodes-primary
| * Remove import columns from projects tablesh-remove-import-columns-from-projectsStan Hu2019-06-191-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21497, we migrated all project import data into a separate table, `project_import_data`. In addition, we also added: ``` ignore_column :import_status, :import_jid, :import_error ``` In https://gitlab.com/gitlab-com/gl-infra/production/issues/908, we observed some of these `import_error` columns consumed megabytes of error backtraces and caused slow loading of projects whenever a `SELECT * from projects` query loaded the row into memory. Since we have long migrated away from these columns, we can now drop these columns entirely.
| * Backport of 12014-incremental-es-wiki-updatesce-12014-incremental-es-wiki-updatesMario de la Ossa2019-06-181-0/+2
| | | | | | | | Bringing in the DB migration and some light changes for CE classes
* | Disallow `NULL` values for `geo_nodes.primary` columnArun Kumar Mohan2019-06-181-2/+2
|/
* Merge branch 'backport-report_approver-migration-to-ce' into 'master'Yorick Peterse2019-06-181-0/+1
|\ | | | | | | | | Backport approval MR rules report_type migration to CE See merge request gitlab-org/gitlab-ce!29766
| * Backport approval MR rules report_type migration to CEbackport-report_approver-migration-to-ceLucas Charles2019-06-171-0/+1
| |
* | Merge branch '57918-encrypt-feature-flags-tokens' into 'master'Kamil Trzciński2019-06-181-1/+3
|\ \ | | | | | | | | | | | | Add migrations needed to encrypt feature flags client tokens See merge request gitlab-org/gitlab-ce!29320
| * | Add migrations needed to encrypt feature flags client tokens57918-encrypt-feature-flags-tokensKrasimir Angelov2019-06-181-1/+3
| | | | | | | | | | | | | | | | | | | | | Make plaintext token column not null, add new token_encrypted column and index on project_id & token_encrypted. Post deployment migration to encrypt existing tokens.
* | | Merge branch 'mc/feature/required-template-inclusion-single-commit-ce' into ↵Grzegorz Bizon2019-06-181-0/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 'master' Enforce template inclusion in pipelines - CE See merge request gitlab-org/gitlab-ce!29296
| * | | Backport CE changesmc/feature/required-template-inclusion-single-commit-ceMatija Čupić2019-06-171-0/+1
| | | | | | | | | | | | | | | | | | | | Backports CE changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14011/
* | | | Merge branch 'ashmckenzie/add-created-at-index-to-events' into 'master'Thong Kuah2019-06-181-0/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add index to events and audit_events tables Closes gitlab-com/Product#309 See merge request gitlab-org/gitlab-ce!29194
| * | | | Add index to events and audit_events tablesashmckenzie/add-created-at-index-to-eventsAsh McKenzie2019-06-181-0/+2
| | |/ / | |/| | | | | | | | | | Index on created_at, author_id
* | | | Merge branch 'issue-62685-new' into 'master'Andreas Brandl2019-06-171-0/+1
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Add index on invite-email to members See merge request gitlab-org/gitlab-ce!29768
| * | | Add index on invite-email to membersyguo2019-06-171-0/+1
| | |/ | |/|