Continuous Deployment

What is CI/CD?

CI/CD stands for Continuous Integration and Continuous Delivery/Deployment — a practice where developers merge code frequently into a shared branch (CI), trigg…

Continuous Integration vs Continuous Deployment

Continuous Integration (CI) is the practice of frequently merging code into a shared branch with each merge automatically built and tested, while Continuous De…

What is a CI/CD Pipeline?

A CI/CD pipeline is the automated sequence of stages — checkout, build, test, and deploy — that takes a code change from commit to running in an environment, w…

What is GitOps?

GitOps is an operational practice where a Git repository is the single source of truth for declarative infrastructure and application configuration, and an aut…

What is Jenkins and How Does It Work?

Jenkins is an open-source, self-hosted automation server that orchestrates build, test, and deployment pipelines, defined as code in a Jenkinsfile and executed…

What is GitHub Actions and How Do Workflows Run?

GitHub Actions is GitHub’s native CI/CD platform where workflows are defined as YAML files in .github/workflows, triggered by repository events, and executed o…

What is GitLab CI/CD and How Does the Pipeline Model Work?

GitLab CI/CD is GitLab’s built-in continuous integration and delivery system, configured through a single `.gitlab-ci.yml` file that defines stages and jobs ex…

What is Argo CD and How Does GitOps Deployment Work?

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes that continuously compares the live cluster state against manifests stored in a Git re…

What is Pipeline as Code?

Pipeline as Code means the CI/CD pipeline’s build, test, and deploy stages are defined in a version-controlled file, such as a Jenkinsfile or a GitHub Actions…

What are Build Artifacts in CI/CD?

A build artifact is the versioned, immutable output produced by a CI pipeline's build stage — such as a compiled binary, a Docker image, or a packaged archive…

What is a Recreate Deployment Strategy?

A recreate deployment strategy fully stops all running instances of the old application version before starting any instances of the new version, meaning there…

How Do Feature Flags Support DevOps Practices?

Feature flags are runtime toggles that let a team deploy new code to production while keeping it hidden or disabled, decoupling the act of deploying code from…

What is Trunk-Based Development?

Trunk-based development is a source-control practice where all developers commit small, frequent changes directly to a single shared branch — the trunk or main…

What Are CI/CD Pipeline Triggers and How Do They Work?

A pipeline trigger is the event that causes a CI/CD pipeline to start running automatically — most commonly a Git push or pull request, but also a scheduled ti…

What Are the Common Git Branching Strategies?

A Git branching strategy is a team-wide convention for how branches are created, named, merged, and released, and the most common ones are Git Flow (long-lived…

Git Flow vs GitHub Flow: What Is the Difference?

Git Flow uses multiple long-lived branches (develop, release/*, hotfix/*, main) to manage scheduled, versioned releases, while GitHub Flow uses just one long-l…

GitOps vs Traditional CI/CD: What Is the Difference?

Traditional CI/CD pushes changes into an environment by having the pipeline itself run `kubectl apply` or similar deploy commands against the cluster, while Gi…