Continuous delivery

Continuous delivery keeps every change ready to release: built, tested and deployable at the push of a button, in small and frequent batches.

Integration, delivery and deployment

  • Continuous integration: every change is merged and tested often.
  • Continuous delivery: every change is always ready to go to production.
  • Continuous deployment: every change that passes goes to production automatically.

The deployment pipeline

A pipeline turns a commit into a release through fixed stages: build, test, deploy to test environments and deploy to production. Every stage that passes adds confidence; any stage that fails stops the line.

Delivery with governance

Regulated organizations can deliver continuously too. The key is to keep authorizations where the risk is, and to make the evidence they need arrive automatically from the pipeline.

How DevGob applies it

DevGob governs the path to production with phases, two committee gates and install evidence, while CI results and releases arrive from GitHub on their own.

Read it in the documentation

Related topics

DevOps automation Automate first what is repetitive, error-prone and frequent: builds, tests, deployments and the links between the work and the code. Continuous testing Continuous testing checks every change as early as possible and keeps the results as evidence for whoever has to authorize the release. Change management in DevOps Change management decides which changes need authorization, who gives it and what evidence is kept — without slowing down the changes that don't.

DevOps with governance, on one record

DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.

Request a workspace Documentation