Skip to content

Using Liquibase with Spring Boot

The purpose of this tutorial is to guide you through the process of using Liquibase as part of your Spring Boot workflow. Spring Boot makes it easy to create standalone, production grade Spring-based applications.


Spring Boot allows you to create Java applications that can be started by using java -jar or war deployments.

With Spring Boot, some of the heavy lifting of configuring beans to set up things like messaging, database connection, migration, and others are already done for you. You only need to add the correct jar file on the classpath to be picked up by the framework for auto-configuration.

Some Spring Boot features include Profiles, Logging, Security, Caching, Spring Integration, Testing, and more.


Ensure you have Java Development Kit (JDK 14+)

Using Liquibase with Spring Boot and the Gradle project

The tutorial describes the use of Spring Boot with the Gradle project. To install Gradle and add it to your path, follow Gradle releases.

Note: To use Spring Boot and Maven, see Using Liquibase with Spring Boot and Maven Project.

To create the project, use Spring Initializer:

  1. Under Project, select Gradle Project.
  2. Select Java as your Language.
  3. Under Spring Boot, select 2.3.4.
  4. For Packaging, select Jar.
  5. Use version 11 for Java.

After selecting your options, the project window needs to look similar to the screenshot:

Click GENERATE to download your project template as a zip file. Extract it and open in your IDE.

Note: Liquibase supports a variety of commands. For now, Spring Boot integrates the update, future-rollback-sql, drop-all, update-testing-rollback, and clear-checksums commands.

Spring Boot offers a subset of the Liquibase configuration options. In the table, the Spring Boot options are listed against the Liquibase options.

Spring Boot Liquibase Description
spring.liquibase.change-log changelog-file changelog configuration path
spring.liquibase.labels labels Comma-separated list of runtime labels to use
spring.liquibase.contexts Contexts Comma-separated list of runtime contexts to use
spring.liquibase.database-change-log-lock-table databaseChangeLogLockTableName Name of table to use for tracking concurrent Liquibase usage
spring.liquibase.database-change-log-table databaseChangeLogTableName Name of table to use for tracking change history
spring.liquibase.default-schema defaultSchemaName Default database schema
spring.liquibase.liquibase-schema liquibaseSchemaName Schema to use for Liquibase objects
spring.liquibase.liquibase-tablespace databaseChangeLogTablespaceName Tablespace to use for Liquibase objects
spring.liquibase.parameters.* parameter.* changelog parameters
spring.liquibase.password password Login password of the database to migrate
spring.liquibase.tag -- Tag name to use when applying database changes. Can also be used with rollbackFile to generate a rollback script for all existing changes associated with that tag
spring.liquibase.url url JDBC URL of the database to migrate. If not set, the primary configured data source is used
spring.liquibase.user username Login user of the database to migrate

To start using Liquibase and Spring Boot with Gradle:

  1. Open the existing Spring Boot file. To find the file, navigate to src/main/resources/
  2. Add the following properties to run Liquibase migrations. Update the values depending on your database requirements:
  1. Create a changelog file: src/main/resources/db/changelog/db.changelog-master.xml. Liquibase also supports the .sql, .yaml, or .json changelog formats. For more information, see Introduction to Liquibase and Getting Started with Liquibase.
  2. Add the following code snippet to your changelog file, including changesets:
<?xml version="1.0" encoding="UTF-8"?>
<changeSet id="202010211812" author="Julius Krah">
    <createTable tableName="house">
        <column name="id" type="bigint">
            <constraints primaryKey="true" primaryKeyName="house_id_pk" />
        <column name="owner" type="varchar(250)">
            <constraints unique="true" uniqueConstraintName="house_owner_unq" />
        <column name="fully_paid" type="boolean" defaultValueBoolean="false"></column>
    <createTable tableName="item">
        <column name="id" type="bigint">
            <constraints primaryKey="true" primaryKeyName="item_id_pk" />
        <column name="name" type="varchar(250)" />
        <column name="house_id" type="bigint">
            <constraints nullable="false" notNullConstraintName="item_house_id_nn" />
    <addAutoIncrement tableName="house" columnName="id" columnDataType="bigint" startWith="1" incrementBy="1" />
    <addAutoIncrement tableName="item" columnName="id" columnDataType="bigint" startWith="1" incrementBy="1" />
    <createSequence sequenceName="hibernate_sequence" incrementBy="1" startValue="1" />
    <addForeignKeyConstraint baseTableName="item" baseColumnNames="house_id" constraintName="item_house_id_fk" referencedTableName="house" referencedColumnNames="id" />
  1. Run your migration with the following command:
./gradlew bootRun

Source code is available at

Tip: If you did not use Spring Initializr, you might not have the gradlew script in your project. In this case, run the following command: gradle bootRun. Both gradle and gradlew create a Java jar for your application. The application jar is located in the build/libs directory of your Gradle project. You can execute the jar file by running java -jar springbootProject-0.0.1-SNAPSHOT.jar.

Related links