- 12 Jul, 2019 1 commit
-
-
Heinrich Lee Yu authored
Updates changed method names and fixes spec failures
-
- 05 Jul, 2019 1 commit
-
-
- 04 Jul, 2019 2 commits
-
-
Zeger-Jan van de Weg authored
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.
-
Nick Thomas authored
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.
-
- 03 Jul, 2019 2 commits
-
-
Maneschi Romain authored
-
Jason Goodman authored
Add released_at field to releases API Add released_at column to releases table Return releases to the API sorted by released_at
-
- 02 Jul, 2019 2 commits
-
-
Krasimir Angelov authored
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.
-
Jarka Košanová authored
- instead of using properties - backward compatibility has to be kept for now
-
- 01 Jul, 2019 1 commit
-
-
Jason Goodman authored
-
- 27 Jun, 2019 1 commit
-
-
Thong Kuah authored
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
-
- 26 Jun, 2019 1 commit
-
-
Patrick Bajao authored
-
- 25 Jun, 2019 5 commits
-
-
Roger Meier authored
-
Mayra Cabrera authored
- 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
-
Peter Leitzen authored
This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.
-
Heinrich Lee Yu authored
Changes migration and all other places the attribute is used
-
Jon Kolb authored
Adds an instance setting to limit display of time tracking values to hours only
-
- 24 Jun, 2019 1 commit
-
-
Vladimir Shushlin authored
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
-
- 21 Jun, 2019 1 commit
-
-
Vladimir Shushlin authored
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
-
- 20 Jun, 2019 1 commit
-
-
Oswaldo Ferreira authored
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.
-
- 19 Jun, 2019 1 commit
-
-
Stan Hu authored
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.
-
- 18 Jun, 2019 2 commits
-
-
Mario de la Ossa authored
Bringing in the DB migration and some light changes for CE classes
-
Arun Kumar Mohan authored
-
- 17 Jun, 2019 8 commits
-
-
Ash McKenzie authored
Index on created_at, author_id
-
Krasimir Angelov authored
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.
-
Matija Čupić authored
Backports CE changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14011/
-
Lucas Charles authored
-
Gabriel Mazetto authored
updated documentation for Geo
-
yguo authored
-
Imre Farkas authored
-
Yorick Peterse authored
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.
-
- 16 Jun, 2019 1 commit
-
-
Luke Duncalfe authored
This backports to CE changes that allow the recording of the repository_type in the table lfs_objects_projects. This is in order to allow future pruning of unreferenced LFS objects, as we will need to know which repository to look in for the LFS pointer file. The EE MR that contains the original code and a full explanation of the changes is https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894 EE Issue https://gitlab.com/gitlab-org/gitlab-ee/issues/9490 Note that there was a lot of CE code changed in the EE MR because we want to allow the wiki repository to also use LFS. See https://gitlab.com/gitlab-org/gitlab-ce/issues/43721. As the wiki is an unlicensed feature, a full backport is required to enable this.
-
- 13 Jun, 2019 3 commits
-
-
Pavel Shutsin authored
-
Jarka Košanová authored
- create tables for storing issue trackers properties - add model and basic logic & spec
-
yguo authored
Clean up issue-62684 Update issue-62684 changelog Update down migrate for issue-62684
-
- 12 Jun, 2019 1 commit
-
-
Rubén Dávila authored
-
- 11 Jun, 2019 4 commits
-
-
yguo authored
Clean up issue-62684 Update issue-62684 changelog Update down migrate for issue-62684
-
yguo authored
Clean up issue-62684 Update issue-62684 changelog
-
Małgorzata Ksionek authored
-
Shinya Maeda authored
In order to optimize the query performance, we should use target project id and target branch intead of cross-joining merge_requests table. Fix schema Fix schema
-
- 06 Jun, 2019 1 commit
-
-
Vladimir Shushlin authored
Save certificate validity time for pages domains on save Fill validity time for existing pages domains in background migration
-