Buddy vs. Liquibase

Springloops is the best tool for deployment to any environment. Especially, the auto-deployment feature on development servers is essential for the early stages of development. The built-in source control mechanisms are a perfect combination of ease of use and a rich feature set that allows the development team to have an easier and more complete view of each part of the project. A section that is lacking is time tracking - but then this is not the main usage of the service.

Incentivized

Liquibase is well suited when there is a need to manage database version. When there are database changes then Liquibase can easily manage, deploy the updates and it can build an automated CI/CD pipelines for databases. Liquibase is less appropriate where there is no change in database schema but that is less likely to happen.

Incentivized

• Easy of use - clear user interface
• Fast deployment to all environments
• Great combination of source control and project management

Incentivized

• It's a useful tool for managing database versions and aiding in the development of database CI/CD pipelines.
• The deployment and management of database updates are simple.
• It provides quality checks to spot problems in DB scripts and DB pipeline views to track changes made to DB.

Incentivized

• We would love to have a more flexible management for resources (users, storage)
• More advanced web hooks would be a plus

Incentivized

• Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
• We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
• Liquibase should rollback the if any one of the changes fails.

Incentivized

Apart from being a great versioning control system Springloops offers the options to automatically deploy code to multiple systems. This feature alone is a determining factor to renew Springloops over and over again. Another important factor is that it offers a full set of tools that help the team during the development cycle. No switching between time-tracking to project management. This is a real time-saver.

Incentivized

We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.

Incentivized

Easy to use, automatic deployments, comments on projects are only a few factors. Multiple servers per project is another must-have feature. User permissions and rights offer granular control on access to the system

Incentivized

Build process is too time consuming and getting extra DB instance takes a toll

Incentivized

I rarely use it but when I need it the team is there. During the initial steps of Springloops, I had close contact with one of the founders. He provided support to me over Skype! He didn't have to but he did. We had a couple of long talks about some issues I was facing. He has there regardless of time. It was a great experience

Incentivized

The support is the only issue they took several hour to respond a simple EMail I believe that this is because of the Time Zone difference. By the time that they respond we already have solve our issues. Another issue is they close the support tickets some time before confirm that the question is solved. They are more focus in close tickets to reach the SLA that in give a real support

Incentivized

the database deployments helped us with increased productivity,
faster delivery and low risk.

Incentivized

Springloops has a built-in feature that is lacking from Bitbucket (at least on the out-of-the-box functionality). Deployment of projects to various servers/development stages. The process is so easy and painless that even remote servers can act as local environments. This is a feature that differentiates Springloops from other solutions that require other tools to perform the same task.

Incentivized

There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were easy wins to be had by implementing its software.

Incentivized

• A total time saver - just commit changes and Springloops can handle the deployments
• Total control of source code and commits - you never have to think about those things again

Incentivized

• We need to re-educate developers to use Liquibase.
• In some cases, it is hard to align when several teams work on the same DB.
• On the other hand, Liquibase provides order and consistency in managing DB changes.
• Evidence and traceability are a plus.

Incentivized