Liquibase CI/CD, best in all!
Overall Satisfaction with Liquibase
For CI/DC (continuous integration and continuous delivery/deployment) and automated code push whenever some code is merged in the concerned branches(staging, dev or the prod). It is set up by the devops team and upon successful generation of PR for the task, code review and merging it is helpful to automatically push code into whatever environment the code is merged into.
Pros
- CI/CD or automated pushing
- easy jumps between different pushes(rollback)
- easy scripts for migration/database script runs
Cons
- adding support for more code versioning platforms
- making the database changes part more fluid and easy to use
- Not much help regarding "how to do's" related to Liquibase on the internet
- Less time consumption in case of deployment
- Automated data migrations and command runs
- Less human help needed overall
IT made it quite easy, the various changes that were made in the database including new table additions and changes in the old tables were done via migrations and were easily downgraded and upgraded from one version to another, whenever there was a need to rollback or just switch to a different version just for the sake of testing in a dev or staging environment. Really helpful!
There are many things done differently and in a smoother way when it comes to Liquibase. The CI/CD setup flow is easier. Switching between the different versions on different environments is really easy. The UI of login portal is user friendly and easy to use. Overall, it has a slight upper hand on the UI and flow side
Do you think Liquibase delivers good value for the price?
Yes
Are you happy with Liquibase's feature set?
Yes
Did Liquibase live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Liquibase go as expected?
Yes
Would you buy Liquibase again?
Yes


Comments
Please log in to join the conversation