Share your experience using Canonical Bazaar

My main use case for Git is for versioning and controlling and sharing my code.

In a recent Laravel project, I used Git to manage versioning and collaboration by adopting a branching strategy. Specifically, main was for stable releases, and stage for ongoing work and feature branches for isolated changes. Each feature branch was shared through frequent commits and pushed to the remote so that teammates could review the work, run it locally, or continue the development without conflicts. Rebase and track history made collaboration smooth, ensured reproducible builds, and provided a safe rollback if a change introduced issues.

I feel that the best features of Git are its reliable branching model and fast commits. The ability to track every change with a full history and accountability is invaluable.

Git's branching model and change tracking have helped my projects significantly, especially in a recent multi-developer Laravel project where several features were developed in parallel. By isolating each feature on its own branch, the team avoided conflicts and could review work incrementally. When a critical bug appeared in production, Git's history and diff made it easier to identify the exact commit that introduced the issue and rollback safely without disrupting the ongoing development. This combination of isolated branches, clear commit history, and reliable rollback capability kept the project stable while allowing fast iteration.

Git has positively impacted my organization by standardizing collaboration, reducing integration conflicts, and making parallel development far more efficient. The branching model allowed teams to work independently without blocking each other. The clear commit history improved code reviews and accountability.

Git works perfectly as is. The CLI works well with Git, and I don't have any recommendations about it.

I have been working in my current field for about six years.

Git deserves a perfect score because it has been around since the '70s and it works flawlessly all these years. Git's reliable branching model and fast commits stand out along with its stability over time.

I don't think that Git has customer support.

The best advice that I can give is that you have to treat Git as a core part of the development process and not just as a storage tool. This way it leads to cleaner collaboration, safer experimentation, and more predictable releases. I would rate this product a perfect ten.

We are currently not using Liquibase, but we have used it earlier for database deployments. I have provided product information on the PeerSpot site.

Liquibase's valuable features include database deployment and rollback scripts, where we kept our scripts in SQL format. When we deployed using CI/CD, it connected to Liquibase and deployed those scripts to the desired database. We integrated it with CI/CD Jenkins to execute all Liquibase operations, and the logs were retained for around two to three months.

Liquibase's adaptive change scripts benefited our database management process significantly. Previously, if someone logged into the database, they could make changes without any information or change orders. We restricted the DB servers to the DB team specifically. Whenever they wanted to execute changes, they had to go through the change order process, and we would not provide them the password until then. We maintained complete logs so that if any database change occurred and an application stopped working, we had change orders to reference and determine whether it was a legitimate change or a normal variation.

Liquibase's rollback functionality impacted our deployment downtime positively. We would take a backup before anything was executed on the database while we had the change order. Once execution occurred, we performed sanity checks by the application team. If the checks passed, we proceeded. If not, we restored the same copy to avoid database outages.

Liquibase is a very powerful tool in terms of database automation.

I have not found many disadvantages with Liquibase. However, it does not have inbuilt rollback management. You have to take your own backup and restore it if there is any failure. It does not have a feature for rolling back or creating a snapshot of the existing database, so those things must be managed manually.

Liquibase could implement rollback compatibility in the future. Additionally, there were checksum errors, and the logs were not reporting properly in Liquibase, so those issues could be fixed.

I used Liquibase for around two and a half years.

They were helpful. We reached out via email or to their community support, and we received immediate responses.

I can rate their job an 8.5 out of 10.

I changed companies, which is why I stopped using Liquibase. The previous organization was still using Liquibase, and there was no switching of the product. However, I moved to a different organization.

I rate Liquibase a nine out of ten. We used the Community Edition for Liquibase.

We used Liquibase's changelog feature extensively. The changelog contains complete information about all the scripts we executed and presents it as event data.

Liquibase's CLI was powerful. We executed scripts through the CLI, and from CI/CD, we called those commands using the CLI.

We built a separate tool for monitoring the databases where we logged the query speed in terms of Liquibase's tracing and monitoring capabilities helping with compliance for our enterprise. We were not using any inbuilt tool from Liquibase. In terms of compliance and audit, we had the challenge that the compliance team would spend weeks gathering manual evidence for audits. We maintained change orders where we kept the change queries that we were going to execute on the production database from the DBA so that everything would be compliant because of these change orders.

My overall review rating for Liquibase is a nine out of ten.