One search. Connected ideas.

Continuous integration checks changes frequently through automated builds and tests. Continuous delivery keeps a verified release ready for deployment, while continuous deployment automatically sends qualifying changes to production. The distinction is the production release decision, not whether any automation exists.

A delivery pipeline turns source changes into a verified, versioned artifact and releases it through controlled environments. Each step should provide evidence that the next step is safe and reproducible. Promoting the same artifact avoids rebuilding slightly different software for each environment.

GitHub Actions defines automated workflows triggered by repository or scheduled events. Workflows contain jobs that run on runners, and jobs contain ordered steps using commands or reusable actions. Artifacts and outputs move results between steps or jobs, while permissions control what the workflow may access.

Continuous integration checks changes frequently through automated builds and tests. Continuous delivery keeps a verified release ready for deployment, while continuous deployment automatically sends qualifying changes to production. The distinction is the production release decision, not whether any automation exists.

A delivery pipeline turns source changes into a verified, versioned artifact and releases it through controlled environments. Each step should provide evidence that the next step is safe and reproducible. Promoting the same artifact avoids rebuilding slightly different software for each environment.

GitHub Actions defines automated workflows triggered by repository or scheduled events. Workflows contain jobs that run on runners, and jobs contain ordered steps using commands or reusable actions. Artifacts and outputs move results between steps or jobs, while permissions control what the workflow may access.

Delivery & cloud learning module