Commit 98c79081 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'docs-fixes-scheduling-on-background-migrations' into 'master'

Cleans up "Scheduling" section on Background Migrations

See merge request gitlab-org/gitlab-ce!32557
parents a2fe68c0 b1fd8466
...@@ -61,8 +61,8 @@ migration classes must be defined in the namespace ...@@ -61,8 +61,8 @@ migration classes must be defined in the namespace
## Scheduling ## Scheduling
Scheduling a migration can be done in either a regular migration or a Scheduling a background migration should be done in a post-deployment migration.
post-deployment migration. To do so, simply use the following code while To do so, simply use the following code while
replacing the class name and arguments with whatever values are necessary for replacing the class name and arguments with whatever values are necessary for
your migration: your migration:
...@@ -283,10 +283,13 @@ the `services.properties` column. ...@@ -283,10 +283,13 @@ the `services.properties` column.
## Testing ## Testing
It is required to write tests for background migrations' scheduling migration It is required to write tests for:
(either a regular migration or a post deployment migration), background
migration itself and a cleanup migration. You can use the `:migration` RSpec - The background migrations' scheduling migration.
tag when testing a regular / post deployment migration. - The background migration itself.
- A cleanup migration.
You can use the `:migration` RSpec tag when testing the migrations.
See [README][migrations-readme]. See [README][migrations-readme].
When you do that, keep in mind that `before` and `after` RSpec hooks are going When you do that, keep in mind that `before` and `after` RSpec hooks are going
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment