Including the tag as a changeSet is the preferred approach in automated pipelines because it ensures the tag is always created at exactly the right point in the changeLog regardless of when the deployment runs. The CLI approach requires the operator to run the tag command before the update, which is easy to forget. To roll back to a tag: liquibase rollback v2.3.0 This reverses all changeSets applied after the tag point, in reverse order. Before executing, you can preview what would happen: liquibase rollbackSQL v2.3.0 A good practice for CI/CD pipelines is tagging the database with the release version at the start of every deployment. If the deployment fails partway through, rolling back to the previous tag restores the exact schema that was stable before the release."> Including the tag as a changeSet is the preferred approach in automated pipelines because it ensures the tag is always created at exactly the right point in the changeLog regardless of when the deployment runs. The CLI approach requires the operator to run the tag command before the update, which is easy to forget. To roll back to a tag: liquibase rollback v2.3.0 This reverses all changeSets applied after the tag point, in reverse order. Before executing, you can preview what would happen: liquibase rollbackSQL v2.3.0 A good practice for CI/CD pipelines is tagging the database with the release version at the start of every deployment. If the deployment fails partway through, rolling back to the previous tag restores the exact schema that was stable before the release." />

Prev Next

Database / Liquibase interview questions

What are Liquibase tags and how do you use rollback to a tag?

A tag in Liquibase is a named marker you apply to the current state of DATABASECHANGELOG — a named checkpoint that records exactly which changeSets have been applied at the time of tagging. Tags are used as rollback targets: instead of counting changeSets or specifying a date, you roll back to a named release like v2.3.0.

You create a tag in two ways:

Via the CLI before a deployment:

liquibase tag v2.3.0

Inline in the changeLog using the tagDatabase change type:

<changeSet id="tag-v2.3.0" author="release-bot">
    <tagDatabase tag="v2.3.0"/>
</changeSet>

Including the tag as a changeSet is the preferred approach in automated pipelines because it ensures the tag is always created at exactly the right point in the changeLog regardless of when the deployment runs. The CLI approach requires the operator to run the tag command before the update, which is easy to forget.

To roll back to a tag:

liquibase rollback v2.3.0

This reverses all changeSets applied after the tag point, in reverse order. Before executing, you can preview what would happen:

liquibase rollbackSQL v2.3.0

A good practice for CI/CD pipelines is tagging the database with the release version at the start of every deployment. If the deployment fails partway through, rolling back to the previous tag restores the exact schema that was stable before the release.

Why is the inline <tagDatabase> changeSet approach preferred over the CLI liquibase tag command?
What is the order in which changeSets are reversed when rolling back to a tag?

Invest now in Acorns!!! 🚀 Join Acorns and get your $5 bonus!

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Earn passively and while sleeping

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.


Webull! Receive free stock by signing up using the link: Webull signup.

More Related questions...

What is Liquibase and what problem does it solve? What is a changeLog in Liquibase? What is a changeSet in Liquibase and how is it identified? What are the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables? What is the difference between Liquibase and Flyway? What are contexts in Liquibase and how do you use them? What are labels in Liquibase and how do they differ from contexts? How does rollback work in Liquibase? What is a Liquibase precondition and why would you use one? How do you integrate Liquibase with Spring Boot? What are Liquibase change types and can you name common ones? What is the Liquibase diff command and when is it useful? What are Liquibase tags and how do you use rollback to a tag? What is runOnChange and runAlways in a Liquibase changeSet? What is the markNextChangeSetRan and markNextChangeSetRanSQL command used for? How do you manage Liquibase changeLog files in a multi-module Maven project? What is the Liquibase updateSQL command and when is it used? What is a Liquibase snapshot and what commands use it? What is the failOnError attribute in a changeSet and when should you set it to false? How does Liquibase handle transactions during migration? What is the Liquibase Hub and what does it provide? How do you use Liquibase with multiple databases or schemas in a single application? What is the Liquibase Pro checksum validity and how do clearCheckSums and validChecksums work? What are Liquibase custom change types and how do you create one? How do you handle large table migrations in Liquibase without causing downtime? What is the Liquibase Maven plugin and how do you run migrations with it? What is the Liquibase status command and how does it differ from validate? What are Liquibase property substitution and how does it work? How do you write Liquibase changeLogs in YAML format? What is the Liquibase formatted SQL changeLog format? What is the Liquibase updateTestingRollback command? How do you use Liquibase with Docker and Testcontainers in integration tests? What is the difference between addColumn with a default value and a nullable column in Liquibase for large tables? What is liquibase.properties and what configuration belongs in it?


Comments & Discussions