Flyway - support for simultaneous versions / multiple branches

Does anyone know a good way to allow larger projects with more engineers working in parallel to manage versions with Flyway ? We often find that during mergers, in order to master, we end conflicting mergers only because 2-3 independent projects needed dB changes and they used the same version number.

In this case, I'm not even sure that the Rails timestamp for version control will work, because you don't necessarily know the order in which the merges will be executed.

Any good tricks to get around this, besides having to re-migrate before merging?

Tom

+4
source share
2 answers

Renumbering is one way.

Another easy way to avoid version number conflicts is to have a board or just a wiki page where every developer can reserve a version number when they start working on it.

Alternatively, Flyway 1.8 will be released soon, and it will include a feature that, if necessary, allows you to reconfigure migration. However, this is not risky in all scenarios.

+3
source

The best way I've seen overcoming version problems between branches is to enable outOfOrder and use a timestamp as the version number

See my answer here: How to use Flyway when working with function branches

0
source

Source: https://habr.com/ru/post/1437658/


All Articles