diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-22 09:08:33 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-22 09:08:33 +0300 |
| commit | 83d8c1d61762898eb4e69878f117cbb2ef5be494 (patch) | |
| tree | b9d0e2071d163a92a19f935761ae3276ac4831cb /doc/development/background_migrations.md | |
| parent | 32d52eb6dd32c58016fa99e05078836cb0dcabde (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/background_migrations.md')
| -rw-r--r-- | doc/development/background_migrations.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/development/background_migrations.md b/doc/development/background_migrations.md index 8a1db615022..746618be50f 100644 --- a/doc/development/background_migrations.md +++ b/doc/development/background_migrations.md @@ -56,6 +56,13 @@ for more details. Make sure that in case that your migration job is going to be retried data integrity is guaranteed. +## Background migrations for EE-only features + +All the background migration classes for EE-only features should be present in GitLab CE. +For this purpose, an empty class can be created for GitLab CE and for GitLab EE it can be extended +For this purpose, an empty class can be created for GitLab CE, and it can be extended for GitLab EE +as explained in the [guidelines for implementing Enterprise Edition features](ee_features.md#code-in-libgitlabbackground_migration). + ## How It Works Background migrations are simple classes that define a `perform` method. A |