What is CI/CD Pipeline?
Definition
Continuous integration means changes are merged and tested frequently, often on every commit, so integration problems surface quickly instead of accumulating until a large, risky merge. Continuous delivery extends this by automating the path to production, either deploying automatically (continuous deployment) or making every tested change ready to deploy with a single approval. Database changes have often sat outside this system: application code moves through CI/CD automatically, while schema changes get applied separately, sometimes manually, on a different schedule. Including the database ChangeLog as a step in the same pipeline closes that gap, so a schema change gets the same automated testing and gated promotion as the application code that depends on it, instead of a separate, less consistent process.
Why including the database in CI/CD matters
An application and the database it depends on usually change together: a new feature often needs both new code and a schema update. When only the code goes through CI/CD and the schema change is applied separately, the two can drift out of sync, a deployed application expecting a column that hasn't been added yet, or a schema change that breaks code still running an older version. Running both through the same pipeline keeps them moving together. Coordinating the two through separate processes and calendars is also simply more overhead than most teams want to maintain, compared to a single pipeline both kinds of change move through.
How database changes fit into CI/CD
A ChangeLog can be checked into the same repository as the application it supports and picked up by the same build system. On each run, the pipeline can validate the ChangeLog (checking for policy violations, for instance), apply it to a test environment, and run tests against the resulting schema, all before the application code built alongside it reaches the same stage. Because the ChangeLog only applies ChangeSets that haven't run yet in a given environment, the pipeline can run repeatedly without reapplying anything twice.
How Liquibase helps
Liquibase integrates with common CI/CD tools including Jenkins and GitHub Actions, so a ChangeLog becomes a step in an existing pipeline rather than a separate deployment mechanism to maintain. Liquibase Secure layers governance onto that same pipeline, running policy checks and capturing audit evidence as part of the pipeline run itself, so database changes get the same automated rigor, and the same record afterward, as the application code they ship alongside, and the same pipeline that tests application code can test the resulting schema at the same time, catching a compatibility problem before either half of the change reaches a shared environment.
