CircleCI Reviews

Liquibase Reviews

CircleCI mentions (66)

• Effortless Code Conventions Review for Pull Request Changes

  CI *(in our case that’s CircleCI) we run it for each *Pull Request. - Source: dev.to / 14 days ago

• The simplest way to automate delivery of your React Native Application

  In this article, we are going to provide simple and detailed step-by-step instruction on how to set up Continuous Delivery for your React Native Android application by using Fabric and CircleCI 2.0. - Source: dev.to / 17 days ago

• How to secure Python Flask applications

  In addition, Snyk can be easily integrated with various IDEs, including Visual Studio Code and PyCharm, as well as CI pipelines, such as Jenkins, CircleCI, and Maven, and workflows. - Source: dev.to / about 1 month ago

• Github Actions to deploy your Terraform code

  Github Actions has many competitors in its category that allow you to run all kinds of code running on containers, such as Gitlab, Jenkins, CircleCI, etc. - Source: dev.to / about 1 month ago

• Automated delivery React / Vue app for each Pull Request.

  It will give you a possibility to find and solve problems faster, release more stable and higher quality products. Here we will use CircleCI, but you can use whatever you need (Jenkins, Travis CI, GitLab CI). - Source: dev.to / about 1 month ago

Liquibase mentions (5)

• How do you guys go about the persistence layer?

  As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

• How do you guys go about the persistence layer? (x-post)

  I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

• Where questioning the scale of a company and its clients its seen bad

  Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

• State based change management tool for Snowflake

  I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago

• Learning SQL and using dll (CREATE,DROP,ALTER)

  Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago