IBM DevOps Deploy vs. Liquibase

IBM UrbanCode Deploy is excellent for code deployments such as Java, .Net, C++, etc. It can also deploy and run SQLs reasonably well. Where it lacks is the ability for executables, Jars, WARs, EARs, etc.

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

• Consistently deploys to multiple environments with no changes to the process. Having reusable processes across environments from Dev to Production make deployments more consistent and easier to manage.
• IBM UrbanCode Deploy has an easy to understand UI, to be able to review if a deployment has successfully completed or not, and details if it did not work. Using the UI is simple and easy to understand.
• Scheduling and approvals are built-in as configured for the deployments. This allows us to use the same deployment process, but get approvals as needed when code is moved up to the upper environments.

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

• IBM UrbanCode Deploy does code deployments easy enough, but configurations or ex deployments are a little more complicated. I work on packaged systems, so most of the code I get is form a vendor that I have to deploy.
• IBM UebanCode Deploy integration into the mainframe world would be ideal. My company uses Mainframe and OpenSystems technologies, and many times there are dependencies between the deployments.

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

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

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

Incentivized

I've not worked directly with IBM UrbanCode Deploy support. My DevOps team administers the environment and deals with that.

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

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

• IBM UrbanCode Deploy has had a positive impact on making deployments much easier and quicker to do. Downtime for a system is greatly reduced and deployments go much smoother as the processes are complete repeatable and not manual.

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