bbrt3 · August 11, 2021 18:23
diff --git a/ContinousDelivery.txt b/ContinousDelivery.txt
 Continous Delivery (CD) is the 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 infrastructure and deployment of a new build.

 Anytime there is a new build artifact available,
 it is automatically placed in the desired environment
 and deployed.

 This means that on top of automated testing, you have an automated release process 
 and you can deploy your application any time by clicking a button.

 DEPLOYING IS MANUAL !!!
diff --git a/ContinousDeployment.txt b/ContinousDeployment.txt
 It goes one step further than continous delivery.
 Each time there is a change approved that passed all stages,
 it gets released to the consumers straight up.
 Without any intervention!
diff --git a/ContinousIntegration.txt b/ContinousIntegration.txt
 It is about develop phase - building and testing code, fully automated.

 Each time you commit code, changes are validated and merged
 to the master branch, and the code is packaged in a build artifact.

 This means that on top of automated testing, you have an automated release process and you can deploy your application any time by clicking a button.
diff --git a/IaaC.txt b/IaaC.txt
 infrastructure as a Code (IaaC) is the management of infrastructure
 (networks, virutal machines, load balancers and connection topology)
 in a descriptive model, using the same versioning as DevOps team uses for source code.

 IaaC treats configuring infrastructure exactly like programming software.
 In effect, this starts to blur the boundaries between writing apps
 and creating the environments they run within.
 Applications can contain scripts that create and orchestrate their own virtual machines.

 IaaC allows VMs to  be managed programatically, eliminating
 the need for the manual configuration, updates and all.

 Because of it developers and ops profesionalls have an
 shared set of job responsibilities.

 Teams can define declarative templates that specify the infrastructure
 required to deploy their solutions.

 There is no single standard syntax for declarative IaC. Different platforms support different, 
 and often multiple file formats, such as YAML, JSON, and XML. 
 As a result, the decision to select a syntax for describing IaC usually comes down to the requirements of the target platform.
	Continous Delivery (CD) is the 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 infrastructure and deployment of a new build.

	Anytime there is a new build artifact available,
	it is automatically placed in the desired environment
	and deployed.

	This means that on top of automated testing, you have an automated release process
	and you can deploy your application any time by clicking a button.

	DEPLOYING IS MANUAL !!!
	It goes one step further than continous delivery.
	Each time there is a change approved that passed all stages,
	it gets released to the consumers straight up.
	Without any intervention!
	It is about develop phase - building and testing code, fully automated.

	Each time you commit code, changes are validated and merged
	to the master branch, and the code is packaged in a build artifact.

	This means that on top of automated testing, you have an automated release process and you can deploy your application any time by clicking a button.
	infrastructure as a Code (IaaC) is the management of infrastructure
	(networks, virutal machines, load balancers and connection topology)
	in a descriptive model, using the same versioning as DevOps team uses for source code.

	IaaC treats configuring infrastructure exactly like programming software.
	In effect, this starts to blur the boundaries between writing apps
	and creating the environments they run within.
	Applications can contain scripts that create and orchestrate their own virtual machines.

	IaaC allows VMs to be managed programatically, eliminating
	the need for the manual configuration, updates and all.

	Because of it developers and ops profesionalls have an
	shared set of job responsibilities.

	Teams can define declarative templates that specify the infrastructure
	required to deploy their solutions.

	There is no single standard syntax for declarative IaC. Different platforms support different,
	and often multiple file formats, such as YAML, JSON, and XML.
	As a result, the decision to select a syntax for describing IaC usually comes down to the requirements of the target platform.