summaryrefslogtreecommitdiff
path: root/spec/db
Commit message (Collapse)AuthorAgeFilesLines
* Add commit_id to draft_notes tablePatrick Bajao2019-08-011-1/+1
| | | | CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14520
* Backport EE changes for the schema specsYorick Peterse2019-07-291-0/+2
| | | | | | This backports two EE specific changes made to the schema changes. We do not yet backport the EE prepend, as this will/can be done when https://gitlab.com/gitlab-org/gitlab-ce/issues/58170 is implemented.
* Remove CommonMetricsImporter patchRyan Cobb2019-07-091-139/+0
| | | | | | 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-091-3/+3
| | | | | 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-091-4/+4
| | | | | | | 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.
* Backport the EE schema and migrations to CEYorick Peterse2019-06-171-4/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This backports all EE schema changes to CE, including EE migrations, ensuring both use the same schema. == Updated tests A spec related to ghost and support bot users had to be modified to make it pass. The spec in question assumes that the "support_bot" column exists when defining the spec. In the single codebase setup this is not the case, as the column is backported in a later migration. Any attempt to use a different schema version or use of "around" blocks to conditionally disable specs won't help, as reverting the backport migration would also drop the "support_bot" column. Removing the "support_bot" tests entirely appears to be the only solution. We also need to update some foreign key tests now that we have backported the EE columns. Fortunately, these changes are very minor. == Backporting migrations This commit moves EE specific migrations (except those for the Geo tracking database) and related files to CE, and also removes any traces of the ee/db directory. Some migrations had to be modified or removed, as they no longer work with the schema being backported. These migrations were all quite old, so we opted for removing them where modifying them would take too much time and effort. Some old migrations were modified in EE, while also existing in CE. In these cases we took the EE code, and in one case removed them entirely. It's not worth spending time trying to merge these changes somehow as we plan to remove old migrations around the release of 12.0, see https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
* Create models for issue trackers data58886-issue-tracker-fieldsJarka Košanová2019-06-131-0/+1
| | | | | - create tables for storing issue trackers properties - add model and basic logic & spec
* Change the schema of the common_metrics.ymlrpereira22019-04-171-21/+23
| | | | | - Change it to the new dashboard syntax described here: https://gitlab.com/gitlab-org/gitlab-ce/issues/60383.
* Fix specsFelipe Artur2019-02-151-2/+2
|
* Add table and model for error tracking settingsReuben Pereira2019-01-071-0/+7
|
* Correct ordering of metricsrpereira22018-12-211-1/+7
| | | | | | | | | | | | Correct the ordering of metrics on performance dashboard. Before common metrics were moved into the DB, metric groups were ordered by the priority defined in the common_metrics.yml file. This commit adds a priority to each metric group in the PrometheusMetric model. It also combines title, priority and required_metrics into one frozen GROUP_DETAILS hash so that the code is clearer. This can be done since there is a fixed set of groups which are not configurable.
* Allow suggesting single line changes in diffsOswaldo Ferreira2018-12-131-1/+2
|
* Backport EE changesKamil Trzciński2018-11-151-1/+7
|
* Validate foreign keys being indexedKamil Trzciński2018-11-151-0/+90
|
* Use Rails.root for CommonMetricsImporterKamil Trzciński2018-09-111-0/+10
|
* Fix common_metrics.ymlKamil Trzciński2018-09-061-1/+1
|
* Test production/development fixtures seedKamil Trzciński2018-09-052-0/+30
|
* Fix static analysisKamil Trzciński2018-09-041-1/+1
|
* Add `# frozen_string_literal: true`Kamil Trzciński2018-09-041-0/+2
|
* Import common metrics into database.Kamil Trzciński2018-09-041-0/+119
| | | | | This MR backports PrometheusMetric model to CE and adds: common, identifier to figure out what kind of metric is used.
* Enable prometheus metrics by defaultFelipe Artur2018-05-071-3/+3
|
* Set ENV['IN_MEMORY_APPLICATION_SETTINGS'] to 'true in ↵Rémy Coutable2018-04-161-1/+6
| | | | | | spec/db/production/settings_spec.rb Signed-off-by: Rémy Coutable <remy@rymai.me>
* Remove superfluous lib: true, type: redis, service: true, models: true, ↵Rémy Coutable2017-07-271-1/+1
| | | | | | services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me>
* Handle case where GITLAB_PROMETHEUS_METRICS_ENABLED is non boolean value by ↵Pawel Chojnacki2017-06-061-0/+12
| | | | defaulting to false
* Make PrometheusTextFormat return proper output terminated with '\n'Pawel Chojnacki2017-06-021-16/+0
| | | | remove file dangling after rebase
* Make production settings fixture use ↵Pawel Chojnacki2017-06-021-2/+2
| | | | | | Gitlab::CurrentSettings.current_application_settings small code formatting changes
* Allow enabling Prometheus metrics via ENV variable when db is seededPawel Chojnacki2017-06-021-0/+46
|
* Move rainbow monkey patch to String to spec_helperGabriel Mazetto2017-05-311-1/+0
|
* Introduce "stub_env" test helper for safely stubbing environment variablesAdam Niedzielski2017-01-091-2/+3
|
* Allow users to seed the initial runner registration token using an ↵DJ Mountney2016-12-011-0/+16
environment variable This is useful for when runner is bundled with gitlab, like in a kubernetes stack, and we want the runner to be able to register with gitlab as soon as they both come up.
View Lorry Controller Status