Liquibase® version 3.8.2 is now available! Get it for free.
News 5 Ways to Fix a Bad Database Change in Liquibase
04 Dec 2019

- and/or -

All Previous Posts >>
Achieving Continuous Delivery at Fidelity Investments with IBM UrbanCode and Datical

Using Version Control Systems with Liquibase

Liquibase utilizes a variety of text-based, human-readable, auto-mergeable formats which allows you to use any version control system of your choice.

Liquibase is “version control friendly” because it executes the changes you give it against a database but doesn’t care where those changes come from. You can manually create them in your machine directory, check them out of a version control system, use a network share file, or they can come from a compressed file like a jar, war, or zip file. What Liquibase cares about is that the file exists and can be read.

What do I need to know about using version control with Liquibase?

If you keep your changeLog files in a version control system, you can perform your normal check-in, check-out, branching, and merging functions. You can run the changeLog at any point from where it is stored and Liquibase will update the database to the expected state.