| Age | Commit message (Collapse) | Author |
|---|
|
This removes old migrations that violate the
FactoriesinMigrationSpecs cop
|
|
Use the `squasher` gem to squash migrations older than the start of 2018
|
|
|
|
|
|
|
|
Automatically update MR merge-ref along merge status
See merge request gitlab-org/gitlab-ce!29569
|
|
Disallow `NULL` values for `geo_nodes.primary` column
Closes gitlab-ee#12061
See merge request gitlab-org/gitlab-ce!29818
|
|
Migrate managed clusters that aren't using managed features to unmanaged
Closes #62772
See merge request gitlab-org/gitlab-ce!29251
|
|
There are clusters that have Kubernetes namespaces
stored which are missing a service account token.
These namespaces are unable to be used for deployments,
so marking the clusters as unmanaged will allow the
platform credentials to be used instead.
|
|
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.
|
|
db/update-geo-nodes-primary
|
|
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.
|
|
|
|
Add migrations needed to encrypt feature flags client tokens
See merge request gitlab-org/gitlab-ce!29320
|
|
Add index to events and audit_events tables
Closes gitlab-com/Product#309
See merge request gitlab-org/gitlab-ce!29194
|
|
Migrate Kubernetes service integration templates to clusters
See merge request gitlab-org/gitlab-ce!28534
|
|
Index on created_at, author_id
|
|
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.
|
|
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.
|
|
These clusters were created before we introduced the
option to manage your own cluster, and not having a
Kubernetes namespace present means that we have tried
and failed to create one - and therefore we cannot manage
your cluster for you.
The 5 minute window should prevent a race condition
where a cluster has only just been created and we
haven't had a chance to create any resources for it
yet.
|
|
|
|
Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration
|
|
This reverts merge request !28743
|
|
Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration
|
|
Reset merge status from mergeable MRs
See merge request gitlab-org/gitlab-ce!28843
|
|
Adds migrations to reset the merge_status of opened,
mergeable MRs. That's required by
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28513
so we're able to sync the status update along merge-ref,
without leaving MRs with a stale merge-ref.
|
|
Now that the column is ignored, we can safely drop the column
|
|
Assume that if an instance level cluster already exists, then the
KubernetesService was not being used, but allow the admin to re-enable
it if required
|
|
The migration uses active record model stubs so that field encryption
can be more easily used.
|
|
|
|
Remove duplicate definition of DOWNTIME
See merge request gitlab-org/gitlab-ce!28294
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
This silences the warning:
20190301081611_migrate_project_migrate_sidekiq_queue.rb:8:
warning: already initialized constant
MigrateProjectMigrateSidekiqQueue::DOWNTIME
|
|
Issues and merge requests imported from GitHub are having state_id
set to null. This fixes the GitHub project importer and schedule
migrations to fix state_id.
|
|
And remove Gitlab::Ci::Trace#deprecated_path as it relies on ci_id
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
This was incorrectly set by a bug in:
https://gitlab.com/gitlab-org/gitlab-ce/issues/54924
Also adds a `batch_size` option to `update_column_in_batches`
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
|
|
This will be further required for supporting multi-assignees MRs
|
|
|
|
`project_migrate_hashed_storage` is now
`hashed_storage:hashed_storage_project_migrate`
|
|
Token column are no longer used as token values are stored digested in
token_digest.
|
|
|
|
|
|
|
|
- Fixes multiple typos on AutoDevops script
- Add an alias to Clusters::Cluster#domain as base_domain, so it's more
descriptive
- Removes unnecessary memoization on qa specs
- Changes migration to a post migration to deal better with traffic on
big instances (like gitlab.com)
|
|
|
|
|
|
|
|
Migrate jobs from `storage_migrator` to
`hashed_storage:hashed_storage_migrator`.
|
