kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Removes regular migrations from background ones 

Specifies that background migrations should be scheduled as post
deployment migrations
This commit is contained in:
Mayra Cabrera 2019-09-04 15:19:40 +00:00 committed by Achilleas Pipinellis
parent a2fe68c010
commit b1fd8466eb
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/development/background_migrations.md
View File

@ -61,8 +61,8 @@ migration classes must be defined in the namespace
## Scheduling
Scheduling a migration can be done in either a regular migration or a
post-deployment migration. To do so, simply use the following code while
Scheduling a background migration should be done in a post-deployment migration.
To do so, simply use the following code while
replacing the class name and arguments with whatever values are necessary for
your migration:
@ -283,10 +283,13 @@ the `services.properties` column.
## Testing
It is required to write tests for background migrations' scheduling migration
(either a regular migration or a post deployment migration), background
migration itself and a cleanup migration. You can use the `:migration` RSpec
tag when testing a regular / post deployment migration.
It is required to write tests for:
- The background migrations' scheduling migration.
- The background migration itself.
- A cleanup migration.
You can use the `:migration` RSpec tag when testing the migrations.
See [README][migrations-readme].
When you do that, keep in mind that `before` and `after` RSpec hooks are going