User: Redirected page to Continuous Delivery

2024-03-16T09:13:40Z

User: Created page with "'''Continuous Delivery (CD)''' is the process to build, test, configure, and deploy from a build to a production environment. Multiple testing or staging environme..."

2021-06-22T20:29:11Z

Created page with "'''Continuous Delivery (CD)''' is the process to build, test, configure, and deploy from a build to a production environment. Multiple testing or staging environme..."

New page

'''Continuous Delivery (CD)''' is the [[Process|process]] to build, test, configure, and deploy from a build to a production environment. Multiple testing or staging environments create a Release Pipeline to automate the creation of [[IT Infrastructure|infrastructure]] and deployment of a new build. Successive environments support progressively longer-running activities of integration, load, and user acceptance testing. [[Continuous Integration]] starts the CD process and the pipeline stages each successive environment to the next upon successful completion of tests.

CD may sequence multiple deployment rings for progressive exposure (also known as "controlling the blast radius"). Progressive exposure groups users who get to try new releases to monitor their experience in rings. The first deployment ring is often a canary used to test new versions in production before a broader rollout. CD automates deployment from one ring to the next and may optionally depend on an approval step, in which a decision maker signs off on the changes electronically. CD may create an auditable record of the approval in order to satisfy regulatory procedures or other control objectives.<ref>Definition - What Does Continuous Delivery Mean? [https://docs.microsoft.com/en-us/devops/deliver/what-is-continuous-delivery Microsoft]</ref>

← Older revision		Revision as of 09:13, 16 March 2024
Line 1:		Line 1:
−	'''Continuous Delivery (CD)''' is the [[Process\|process]] to build, test, configure, and deploy from a build to a production environment. Multiple testing or staging environments create a Release Pipeline to automate the creation of [[IT Infrastructure\|infrastructure]] and deployment of a new build. Successive environments support progressively longer-running activities of integration, load, and user acceptance testing. [[Continuous ~~Integration~~]] ~~starts the CD process and the pipeline stages each successive environment to the next upon successful completion of tests.~~	+	#REDIRECT [[Continuous Delivery]]
−
−	CD may sequence multiple deployment rings for progressive exposure (also known as "controlling the blast radius"). Progressive exposure groups users who get to try new releases to monitor their experience in rings. The first deployment ring is often a canary used to test new versions in production before a broader rollout. CD automates deployment from one ring to the next and may optionally depend on an approval step, in which a decision maker signs off on the changes electronically. CD may create an auditable record of the approval in order to satisfy regulatory procedures or other control objectives.<ref>Definition - What Does Continuous Delivery Mean? [https://docs.microsoft.com/en-us/devops/deliver/what-is-continuous-delivery Microsoft]</ref>

Continuous Delivery (CD) - Revision history

User: Redirected page to Continuous Delivery

User: Created page with "'''Continuous Delivery (CD)''' is the process to build, test, configure, and deploy from a build to a production environment. Multiple testing or staging environme..."