Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/db
AgeCommit message (Collapse)Author
2019-08-26Add captcha if there are multiple failed login attemptsMałgorzata Ksionek
Add method to store session ids by ip Add new specs for storing session ids Add cleaning up records after login Add retrieving anonymous sessions Add login recaptcha setting Add new setting to sessions controller Add conditions for showing captcha Add sessions controller specs Add admin settings specs for login protection Add new settings to api Add stub to devise spec Add new translation key Add cr remarks Rename class call Add cr remarks Change if-clause for consistency Add cr remarks Add code review remarks Refactor AnonymousSession class Add changelog entry Move AnonymousSession class to lib Move store unauthenticated sessions to sessions controller Move link to recaptcha info Regenerate text file Improve copy on the spam page Change action filter for storing anonymous sessions Fix rubocop offences Add code review remarks Fix schema Update schema version
2019-08-26Merge branch 'security-12-1-enable-image-proxy' into '12-1-stable'GitLab Release Tools Bot
Use image proxy to mitigate stealing ip addresses See merge request gitlab/gitlabhq!3231
2019-08-20Add active_jobs_limit to plans tableFabio Pitino
This is a port from EE changes where we introduce a new limit for Plan model. https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/1182
2019-08-15Add support for using a Camo proxy serverBrett Walker
User images and videos will get proxied through the Camo server in order to keep malicious sites from collecting the IP address of users.
2019-07-17Add rule_type to approval_project_rulesLucas Charles
Adds migration to introduce non-regular rule_types to approval_project_rules
2019-07-17Fix wrong pages access level defaultVladimir Shushlin
- Set access level in before_validation hook - Add post migration for updating existing project_features
2019-07-16Migrate null values for users.private_profileAdam Hegyi
- Background migration for changing null values to false - Set false as default value for private_profile DB column
2019-07-15Reorder fields in boards schema to match EEStan Hu
This eliminates conflicts between CE and EE db/schema.rb files.
2019-07-14Reorder application settings in db/schema.rb to match EEStan Hu
This makes the CE and EE tables consistent and ensures changes in the schema for the CE version don't cause conflicts with EE.
2019-07-12Merge branch 'id-clean-up-mr-assignees-migration' into 'master'Andreas Brandl
Add cleanup migration for MR's multiple assignees See merge request gitlab-org/gitlab-ce!30269
2019-07-12Merge branch 'bvl-rename-routes-after-user-rename' into 'master'Jan Provaznik
Set the name of a user-namespace to the user name See merge request gitlab-org/gitlab-ce!23272
2019-07-12Upgrade to Rails 5.2Heinrich Lee Yu
Updates changed method names and fixes spec failures
2019-07-10Add a rubocop for Rails.loggerMayra Cabrera
Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
2019-07-10Rename Gitlab::Importers moduleRyan Cobb
In order to avoid confusion between Gitlab::Importers module and other like named modules, this renamed it to Gitlab::DatabaseImporters.
2019-07-10Remove CommonMetricsImporter patchRyan Cobb
Remove CommonMetricsImporter patch and change all references to CommonMetrics::Importer. Move specs into their appropriate folders. Also cleans up some common_metric importer namespacing.
2019-07-10Move importers to lib folderRyan Cobb
This moves our metric importers into the lib folder. This will allow them to be autoloaded instead of having to explicitly require them.
2019-07-10Refactor common metrics importerRyan Cobb
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.
2019-07-09Fix incorrect namespaces & route for user-routesBob Van Landuyt
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
2019-07-09Add cleanup migration for MR's mutliple assigneesIgor Drozdov
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
2019-07-05Merge branch 'ce-10283-notifications-for-ci-minutes-quota-limit-approaching' ↵James Lopez
into 'master' Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14328 See merge request gitlab-org/gitlab-ce!30003
2019-07-05Merge branch 'zj-remove-stale-feature-flag-keys' into 'master'Andreas Brandl
Remove unused Gitaly feature flags See merge request gitlab-org/gitlab-ce!30302
2019-07-05Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14328Rubén Dávila
2019-07-04Fix call to removed GitPushServiceMarkus Koller
2019-07-04Remove unused Gitaly feature flagsZeger-Jan van de Weg
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.
2019-07-04Allow asynchronous rebase operations to be monitoredNick Thomas
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.
2019-07-03Add Grafana to Admin > Monitoring menu when enabledManeschi Romain
2019-07-03Merge branch '44990-remove-old-i' into 'master'Nick Thomas
Remove old migration specs that violate FactoriesInMigrationSpecs See merge request gitlab-org/gitlab-ce!30280
2019-07-03Show upcoming status for releasesJason Goodman
Add released_at field to releases API Add released_at column to releases table Return releases to the API sorted by released_at
2019-07-02Remove old migrations and specsHeinrich Lee Yu
This removes old migrations that violate the FactoriesinMigrationSpecs cop
2019-07-02Add username to deploy tokensKrasimir Angelov
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.
2019-07-02Merge branch '63690-issue-trackers-title' into 'master'Dmitriy Zaporozhets
Use title and description fields for issue trackers Closes #63690 See merge request gitlab-org/gitlab-ce!30096
2019-07-02Use title and description fields for issue trackersJarka Košanová
- instead of using properties - backward compatibility has to be kept for now
2019-07-02Bring the InitSchema migration up to standardNick Thomas
2019-07-02Squash old migrationsNick Thomas
Use the `squasher` gem to squash migrations older than the start of 2018
2019-07-01Add Migration for Strategies Column on operations_feature_flag_scopesJason Goodman
2019-07-01Merge branch 'db-fixtures' into 'master'Sean McGivern
db.fixtures: use print instead of puts See merge request gitlab-org/gitlab-ce!30134
2019-07-01Merge branch 'add-clusters-to-deployment' into 'master'Lin Jen-Shin
Add clusters association to deployment See merge request gitlab-org/gitlab-ce!29960
2019-06-28Merge branch '3264-project-aliases-ce' into 'master'Bob Van Landuyt
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14108 See merge request gitlab-org/gitlab-ce!29604
2019-06-27db.fixtures: use print instead of putseyjhbb@gmail.com
2019-06-27Add cluster_id to deployments table as an FKThong Kuah
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
2019-06-26Merge branch 'refactor/remove-sentry-from-app-settings' into 'master'Stan Hu
Remove Sentry settings from application settings See merge request gitlab-org/gitlab-ce!28447
2019-06-26Create project_aliases tablePatrick Bajao
2019-06-25refactor(db): remove Sentry from application settings, disable_ddl_transactionRoger Meier
2019-06-25refactor(db): remove Sentry from application settingsRoger Meier
2019-06-25refactor: remove Sentry from application settingsRoger Meier
2019-06-25 Add two new ActiveRecord modelsMayra Cabrera
- 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
2019-06-25Revert "Revert to `id: :integer`"Peter Leitzen
This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.
2019-06-25Merge branch 'sh-recover-ee-schema-backport-migration-failure' into 'master'Rémy Coutable
Prevent EE backport migrations from running if CE is not migrated Closes #63612 See merge request gitlab-org/gitlab-ce!30002
2019-06-25Prevent EE backport migrations from running if CE is not migratedStan Hu
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> ```
2019-06-25Rename to time_tracking_limit_to_hoursHeinrich Lee Yu
Changes migration and all other places the attribute is used
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-15 05:38:28 +0300