Bitbucket vs. Liquibase

As a team we need to push code into the repo on daily basis, Bitbucket has proven that is a reliable and secure server to save and get the code available in no time. The administration part is really easy and there's an extra tool for every developer profile either if you want to use the console or a GUI like Sourcetree.

Incentivized

Store versions of DB's and Schemas this is useful for every software developer company that works with Databases. Now days al the software use a DB and control those changes are a must. have the power to rollback safe has change the way that we work. This increase speed in development while increase the business confidence.

Incentivized

• Very easy to integrate with other DevOps tools like Jenkins and with project/workflow management tools like JIRA.
• Very efficient in managing security and compliance standards for code, especially during pull requests, merge requests, branching, etc.
• Very robust in performance, especially the cloud and datacenter versions hardly hit any performance issues and supports more than 2000+ developers in my company.

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

• The code management UI is a bit rough around the edges and difficult to work with.
• BitBucket does not have the same simplified PR management tools as other competitors.
• It's not as easy to integrate 3rd party apps as other competitors.

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

All products have room for improvement. The system improves over time with better and better integrations and I look forward to even more features without paying extra! The system has increased transparency across my organization and with this transparency comes increased throughput on projects. I don't think I can go back to any other system and we are definitely married to this product.

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

The architecture of Bitbucket makes it more easily scalable than other source code management repositories. Also, administration and maintaining the instance is very easy. It integrates with JIRA and other CI/CD applications which makes it more useful to reduce the efforts. It supports multiple plugins and those bring a lot of extra functionality. It increases the overall efficiency and usefulness of Bitbucket.

Incentivized

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

Incentivized

The customer support provided by Atlassian (Bitbucket's parent company that also makes Jira, Confluence, etc.) is very helpful. They seem to be very concerned about any issues reported with their products and even just questions about functionality. They are constantly improving the products with new features in nearly every release. Plus they have a plethora of online documentation to reference.

Incentivized

Liquibase's customer support is at the top of my list of all vendors I've ever worked with over my 12 years of experience. They work directly with you to be successful, and response time is second to none. Liquibase is committed to getting customers up and running and - more importantly - successful in their organization and becoming champions of the product.

Incentivized

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

Incentivized

For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more familiar tool compared to GitLab. Bitbucket won out because of its close integration with Jira and being in the Atlassian family. It was also cheaper than GitHub. As we started with Jira, Bitbucket addition became a natural next step for us. We really liked Bitbucket and stayed with it but we do know we have great options in the form of GitHub and GitLab should we need to scale fast.

Incentivized

To be honest, the option of having a free community plan to start testing in a test environment, followed by taking it in production a few months is a great way to evaluate wether or not to do the subscription based plan.

Incentivized

• It's allowed for a lot of automation in terms of development workflows. It lets us pursue CI/CD approaches and get releases out faster
• It has let us get our infrastructure configuration into VCS, which further improves our automation abilities.
• It has aided in keeping track of changes, and allows us to keep workflows organized so we can track the status of development

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