Continuous Integration

What Techniques Keep Test Databases Isolated from Each Other?

Test database isolation is achieved by giving each test (or each test worker) its own scoped data boundary — through a per-test transaction rollback, a per-tes…

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 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 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 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…

Declarative vs Scripted Jenkinsfile: What Is the Difference?

A Declarative Jenkinsfile uses a fixed, structured syntax (pipeline { agent { } stages { } } blocks) that is easier to read, validate, and lint, while a Script…

How Does Caching Work in a CI/CD Pipeline?

CI/CD pipeline caching stores the outputs of expensive, repeatable steps — downloaded dependencies, compiled build artifacts, Docker image layers — keyed by a…

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…