Continuous Delivery (CD) Tools logopeterindia.net
Knowledge Hub

Continuous Delivery Tools: Release Pipelines, GitOps & Release Orchestration

Continuous delivery tools — release pipelines, orchestration, GitOps delivery and cloud delivery services that keep software always ready to release.

30 topics•5 categories•Updated November 19, 2026

Concepts & Practices

6 entries

Continuous delivery keeps every change in a releasable state and automates the path from commit to production-ready, with the release itself a business decision. It adds environments, approvals, promotion and release orchestration on top of continuous integration.

Pipeline & Release Orchestration Platforms

6 entries

Model pipelines, environments, approvals and promotion.

GitOps & Kubernetes Delivery

3 entries

Declarative delivery driven by Git.

Cloud Delivery Services

4 entries

Provider-managed delivery.

More Delivery Resources

6 entries

Further delivery tools and references.

Related Pages

5 entries

Neighbouring pages on this site.

Frequently Asked Questions

What is continuous delivery?

A practice where every change is automatically built, tested and prepared so it can be released to production at any time, with the release triggered by a person or business decision.

What is the difference between continuous delivery and continuous deployment?

In continuous delivery the final push to production is a manual decision; in continuous deployment every change that passes the pipeline is released automatically.

What does a continuous delivery tool do?

It models the pipeline and environments, promotes artifacts between stages, enforces approvals and policies, and records what is deployed where.

Argo CD or Spinnaker?

Argo CD (and Flux) suit Kubernetes-centred teams who want Git as the source of truth; Spinnaker suits multi-cloud delivery with rich deployment strategies; Harness and Octopus suit teams wanting a commercial release platform.

What is the current Argo CD release?

On GitHub in October 2026 Argo CD v3.5.6 was marked latest (20 October), with v3.4.12 and v3.3.17 released the same week. Argo CD makes a minor release every three months and patches only the three most recent minor versions. The 3.4 to 3.5 upgrade notes say Helm was upgraded to 4.2.0, so Helm 4 now renders all charts and an app's helm.version v3 setting is ignored, plain-HTTP OCI registries need --insecure-oci-force-http, UI extensions must be rebuilt for React 19, and GnuPG signature verification was replaced by Source Integrity. Argo is a CNCF graduated project.