Share your experience using Canonical Bazaar

My main use case for Liquibase is database-as-code, which we use for creating table schemas, maintaining migrations, and ensuring that in production, if rollbacks happen, then it's more controlled than running raw SQL.

I can give you a quick specific example of how I've used Liquibase for migration. Although we have not used it for rollbacks until now, we do use it for managing our scripts during migration.

Liquibase is a database-as-code provider, and that is pretty much how we use it.

The best features Liquibase offers include CI/CD integration, which we really appreciate because we didn't have a lot of issues integrating it into our existing CI pipelines, and the changeset and changelog, which are the source of truth that effectively tell us how the database changes are taking effect.

The CI/CD integration helped my workflow by improving visibility with the changelog and changeset. For the CI part, Maven and Gradle builds are already available, so we just use the Maven plugin and it was pretty straightforward.

There is something called Liquibase Validate as well, which helps with pre-deployment checks. We use the update SQL command for dry-run approvals.

Liquibase has positively impacted my organization by providing a way to manage database migrations instead of maintaining raw SQL, which comes with the issue of not being able to track certain schema updates or new table creations. With Liquibase, you have that history through the changelog and changeset tables, which maintain that history of changes.

Liquibase can be improved by addressing the issue that changelog files could conflict with Git if they're not modularized properly. While we create one file per feature, rollbacks are not magical and require significant consideration, and large diff operations can also be very slow, affecting performance.

We only use MySQL for now, so there's nothing related to any exotic database features, and we're not consuming anything on that side either.

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

My major use case for Bitbucket Server is that it is a source code repository. We are using it to store our application source code, and we are tracking the check-in, check-out, and all the activities.

The biggest benefit I see from Bitbucket Server is that it is providing all the features which Git is providing. Bitbucket Server is using Git as a source code main tool, and it has all the features that any source code repository can provide. A plus point is that we can install it on-premises and manage it easily.

Using Bitbucket Server helps me easily track my code changes and where they belong, which saves a lot of time and effort. Without Bitbucket Server, it is very difficult to track the code and changes.

The integration with Jira helps me personally with project tracking because Bitbucket Server is a source code repository. We have our SDLC lifecycle in Jira. Every change or every feature request is created as a ticket in Jira, and this ticket is linked with Bitbucket Server repository. Any changes to the code linked to that feature will go to the repository, and we can track that this is the code changed by this feature.

There are certain features in Bitbucket Server that could be better or enhanced, which would make our life easier. One limitation is that we can control granular permissions, but there are some limitations on the granularity of the permissions. We cannot deny access at a branch level; there are some tricky areas, so Bitbucket Server should provide more flexible configuration for granular permissions.

I have been using Bitbucket Server for almost eight years.

Bitbucket Server is quite stable, and I did not see any performance issues.

Regarding the scalability of Bitbucket Server, to be honest, we don't have much requirement in terms of scalability because we have a very small user base, but I can say that Bitbucket Server is quite scalable because it is a server-side solution, and we can scale it vertically easily.

The support from Atlassian is actually good. Overall, I would rate it as good support from Atlassian.

If I had to rate the support between one and ten, I would give them nine points. I cut one point maybe because sometimes we are unable to find the solution easily; we have to dig too much, and sometimes the solution is there, but finding the right solution becomes difficult because there are so many things that create confusion.

Positive

I have worked with something similar to Bitbucket Server, specifically Team Foundation Server.

I have also worked on GitHub.

Bitbucket Server installation is a little bit complicated, and it requires vendor support most of the time.

The complication I face while installing Bitbucket Server is that because we are using it on-premises, when we upgrade Bitbucket Server or install it on a new server, it requires Java Virtual Machine, and sometimes the Java Virtual Machine compatibilities are a problem. There are also other configuration issues, such as when integrating with Jira, Bitbucket Server configuration requires SSL from the back end, so those complexities require troubleshooting and maintenance from our side.

Bitbucket Server license is affordable.

The comparison between Bitbucket Server and TFS depends on the requirements. If you have an Atlassian product suite, you should use Bitbucket Server because it easily integrates with other Atlassian products such as Jira, Bamboo, and Confluence, as well as Fisheye and Crucible. However, if you are not using Atlassian products, other solutions might be better.

I am working with Bitbucket Server today, and there is no issue.

I am not using the pull requests feature.

Bitbucket Server by itself is not very collaborative, but if I use Bitbucket Server with other products, such as Atlassian's other products, it will become collaborative.

We have an integration with Jira.

We are not using Git large file storage in Bitbucket Server.

The granular access settings in Bitbucket Server are quite granular. I can give access at the project level, repository level, or branch level also, which gives all the options.

We purchased Bitbucket Server through an integrator.

I would rate this product a nine out of ten overall.