| Age | Commit message (Collapse) | Author |
|---|
|
Adds migration to introduce non-regular rule_types to
approval_project_rules
|
|
- Set access level in before_validation hook
- Add post migration for updating existing project_features
|
|
- Background migration for changing null values to false
- Set false as default value for private_profile DB column
|
|
This eliminates conflicts between CE and EE db/schema.rb files.
|
|
This makes the CE and EE tables consistent and ensures changes in the
schema for the CE version don't cause conflicts with EE.
|
|
Add cleanup migration for MR's multiple assignees
See merge request gitlab-org/gitlab-ce!30269
|
|
Set the name of a user-namespace to the user name
See merge request gitlab-org/gitlab-ce!23272
|
|
Updates changed method names and fixes spec failures
|
|
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
|
In order to avoid confusion between Gitlab::Importers module and other
like named modules, this renamed it to Gitlab::DatabaseImporters.
|
|
Remove CommonMetricsImporter patch and change all references to
CommonMetrics::Importer. Move specs into their appropriate folders. Also
cleans up some common_metric importer namespacing.
|
|
This moves our metric importers into the lib folder. This will allow
them to be autoloaded instead of having to explicitly require them.
|
|
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.
|
|
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
|
|
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
|
|
into 'master'
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14328
See merge request gitlab-org/gitlab-ce!30003
|
|
Remove unused Gitaly feature flags
See merge request gitlab-org/gitlab-ce!30302
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
Remove old migration specs that violate FactoriesInMigrationSpecs
See merge request gitlab-org/gitlab-ce!30280
|
|
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
|
This removes old migrations that violate the
FactoriesinMigrationSpecs cop
|
|
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.
|
|
Use title and description fields for issue trackers
Closes #63690
See merge request gitlab-org/gitlab-ce!30096
|
|
- instead of using properties
- backward compatibility has to be kept for now
|
|
|
|
Use the `squasher` gem to squash migrations older than the start of 2018
|
|
|
|
db.fixtures: use print instead of puts
See merge request gitlab-org/gitlab-ce!30134
|
|
Add clusters association to deployment
See merge request gitlab-org/gitlab-ce!29960
|
|
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14108
See merge request gitlab-org/gitlab-ce!29604
|
|
|
|
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
|
|
Remove Sentry settings from application settings
See merge request gitlab-org/gitlab-ce!28447
|
|
|
|
|
|
|
|
|
|
- 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
|
|
This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.
|
|
Prevent EE backport migrations from running if CE is not migrated
Closes #63612
See merge request gitlab-org/gitlab-ce!30002
|
|
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>
```
|
|
Changes migration and all other places the attribute is used
|
|
Adds an instance setting to limit display of time tracking
values to hours only
|
|
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
|
|
Automatically update MR merge-ref along merge status
See merge request gitlab-org/gitlab-ce!29569
|
|
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
|
