Instant feedback means better code & more secure databases. Here are two ways your team can implement quality checks for database changes.
Using quality checks for database changes on demand
A developer pulls the latest changelog and quality checks from source code control & creates new database code.
Developer runs the check command.
If the code fails any quality check, the developer is alerted to rework the code before committing it.
If the code passes all quality checks, the developer submits pull request with an updated changelog that includes the Liquibase quality checks output for future reference and faster approval.
Using quality checks for database changes in automation
Add Liquibase quality checks as a build step in automation.
Quality check settings are automatically retrieved.
The Liquibase checks command is run before developers can commit their database code.
If code fails any quality check, the process returns a warning so that the code doesn’t get promoted upstream. If the code passes, the job proceeds as configured.
Want more technical details?
View quality checks documentation for more information on how to configure and use quality checks.