Jan Provaznik
|
0fc9f9d3e7
|
Add version 4.2 to all existing migrations
DB schema generated by a migration may look different in
rails 4 and 5 (because rails 5 may use different default values).
For this reason it's important to explicitly set for which rails
version a migration was written for.
See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
|
2018-11-22 13:18:28 +01:00 |
|
Grzegorz Bizon
|
dbee81480b
|
Reschedule pipeline stages migration to run it again
|
2018-04-05 10:54:33 +02:00 |
|
Grzegorz Bizon
|
2f3f9a6bb0
|
Separate adding and removing index from stages migration
|
2018-02-20 14:00:03 +01:00 |
|
Grzegorz Bizon
|
2d027056f9
|
Add index before going through builds in a migration
|
2018-02-20 13:37:59 +01:00 |
|
Grzegorz Bizon
|
dfef5437a2
|
Use a helper to schedule pipeline stages migration
|
2018-02-16 12:28:34 +01:00 |
|
Grzegorz Bizon
|
6cb5b7c872
|
Recover from unique constraint violation in stages migration
|
2018-02-15 10:13:20 +01:00 |
|
Grzegorz Bizon
|
8488c98e70
|
Schedule pipeline stages migration every 5 minutes
[ci skip]
|
2018-02-13 16:18:09 +01:00 |
|
Grzegorz Bizon
|
acc70f7da1
|
Move pipeline stages background migration in time
|
2018-02-12 13:23:03 +01:00 |