Likelihood to Recommend CircleCI is perfect for a CI/CD pipeline for an app using a standard build process. It'll take more work for a complex build process, but should still be up to the task unless you need a lot of integrations with other tools. If you have a big team and can spare someone to focus full time on just the CI/CD tools, maybe something like Jenkins is better, but if you're just looking to get your app built, tested, and delivered without a huge amount of effort, CircleCI is probably your preferred tool.
Read full review 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.
Read full review Pros Multiple builds can be run at the same time in parallel. The CircleCI web interface (UI/UX) is very easy to understand and use. Easy Configuration to learn and use. Just a single configuration YAML file. Many integrations. We use the GItHub, Slack, and DataDog integrations. Read full review 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. Read full review Cons The "phases" their config file uses to separate out options seem very arbitrary and are not very helpful for organizing your config file No way that I know of to configure which version of MongoDB you use. You have to write your own shell script to download and start MongoDB if you want a specific version. Hard to access build artifacts in the UI Read full review 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. Read full review Likelihood to Renew 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.
Read full review Usability CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in
Read full review Build process is too time consuming and getting extra DB instance takes a toll
Read full review Performance It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Read full review Support Rating Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Read full review 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.
Read full review Implementation Rating the database deployments helped us with increased productivity, faster delivery and low risk.
Read full review Alternatives Considered Circle was the first CI with simple setup, great documentation, and tight integration with
GitHub . Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when we switched.
Read full review 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.
Read full review Return on Investment It has eased the burden of standardizing our testing and deployment, making onboarding new developers much faster, and having to fix deployment mistakes much less often. It allows us to focus our process around the GitHub workflow, ignoring the details of whatever environment the thing we're working on is actually hosted in. This saves us time. Read full review 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. Read full review ScreenShots