Content

Content

Source phase

1. During the source phase, developers check changes into a source code repository.

2. Many teams require peer feedback on code changes before shipping code into production.

3. Solution:

   1. CodeCommit

Build phase

1. During the Build phase, an application’s source code is built and the quality of the code is tested on the build machine.

2. Solution:

   1. CodeBuild

3. Test phase

   1. The goal of the test phase is to perform tests that cannot be done during the build phase and that require the software to be deployed to a production-like stage.

   2. Often, these tests include testing integration with other live systems, load testing, UI testing, and penetration testing.

   3. Solution:

      1. Third Party Tooling

4. Production phase

   1. Finally, code gets deployed to production.

   2. Solution:

      1. CodeDeploy

Complete Cycle Solutions:

1. CodePipeline

2. CodeStar enables you to quickly develop, build, and deploy applications on AWS.

Continuous integration (CI) is the practice of checking in your code continuously and verifying each change with an automated build and test process.

Every code check-in initiates a build

1. Builds are fully automated

2. Tests validate every check-in

Benefits:

1. Instant feedback for developers - The build must remain fast.

2. Minimizes the impact of broken builds - Bugs don’t accumulate.

3. Drives the culture of small, frequent releases.

Continuous delivery extends continuous integration to include testing out to production-like stages and running verification testing against those deployments.

It has some form of manual intervention between a code check-in and when that code is available for customers to use.

Benefits

1. Developers are no longer thinking about unique cases; the cognitive load is reduced.

2. You are no longer implementing a barrage of tests on a continuous basis, detecting regressions against small changes.

3. You no longer have weekly or nightly large number of changes from hundreds of developers.

4. 
   

Continuous deployment

1. Continuous deployment extends continuous delivery and is the automated release of software to customers from check-in through to production without human intervention. Continuous deployment reduces the time for your customers to get value from the code your team has just written, with the team getting faster feedback on the changes you made. This fast customer feedback loop enables you to iterate quickly, allowing you to deliver more valuable software to your customers quicker.

Build stage – takes the source from the repo and builds an immutable deployment artifact bundle

Release stage – takes the deployment artifact and combines it with the environment’s configuration

Run stage – runs the application in the target environment, running processes against the selected release

Content

Content