<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci-Cd on Devops Monk</title><link>https://devops-monk.com/tags/ci-cd/</link><description>Recent content in Ci-Cd on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>CI/CD Integration: GitHub Actions Pipeline for Database Deployments</title><link>https://devops-monk.com/tutorials/liquibase/liquibase-cicd-github-actions/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/liquibase/liquibase-cicd-github-actions/</guid><description>The Liquibase commands covered in Articles 5 and 16 become reliable only when they run automatically on every change. A developer who remembers to run futureRollbackSQL before merging is better than one who doesn&amp;rsquo;t — but a pipeline that enforces it is better than both.
This article builds a complete GitHub Actions pipeline: PR validation gates that block merges when rollback is missing, a staging deployment workflow, and a production deployment workflow with mandatory tagging and pre-generated rollback files.</description></item></channel></rss>