Skip to content

Latest commit

 

History

History
34 lines (21 loc) · 1.83 KB

release_manager.md

File metadata and controls

34 lines (21 loc) · 1.83 KB
layout title
default
Liquibase for Release Managers

Liquibase for Release Managers

Prepare for deployment problems

Releases don't always go as planned, and Liquibase helps you ensure contingency plans are correct before each release. As you near a release, besides checking the updateSql output, you can also run futureRollbackSql which will output the SQL needed to bring a fully updated database back to the current state.

No change is forgotten

Liquibase tracks which changelog statements have run against each database, so you no longer have to manually track what statements have been run against each database and which have not.

Sanity checks

Liquibase ships with several tools you can use to make sure changes are being applied correctly, check current database state, and that nobody is sneaking in changes out of process.

  • The status and validate commands report on what changeSets have not yet been ran and checks the changelog for errors.
  • The diff command reports on differences between databases to ensure that two fully updated databases are truly identical
  • The dbdoc command generates documentation on the current database structure and its changes over time

Enterprise features with Datical

Beyond all the standard Liquibase functionality, Datical lets you


Liquibase for DBAs | QA | Developers