This document defines a CI/CD pipeline for PHP applications using AWS services like CodeBuild and CodePipeline. It discusses setting up continuous integration with a source control system, build system, testing, code reviews, and branching strategies. For continuous delivery, it covers deploying code changes automatically to a testing environment, enabling manual approvals, and deployment strategies like blue/green deployments using Elastic Beanstalk. The goal is to define a simple yet robust CI/CD pipeline to find bugs quickly, improve quality, and reduce release times.

1. Building A
C I / C D
Pipeline For
Php Apps
By Juan Manuel Torres

2. Motivation
2

3. 3
Why Do
We Need A
Pipeline?
Automation

4. Todays
Objective
4
Define A Simple Ci/Cd
Pipeline For X Application

5. Technologies
5

6. C I

7. What Is C I?
7
Definition according to AWS:
Continuous integration is a DevOps software development practice where developers
regularly merge their code changes into a central repository, after which automated
builds and tests are run.
Continuous integration most often refers to the build or integration stage of the software
release process and entails both an automation component (e.g. a CI or build service) and
a cultural component (e.g. learning to integrate frequently). The key goals of continuous
integration are to find and address bugs quicker, improve software quality, and reduce the
time it takes to validate and release new software updates.[1]

8. Requirements
8

9. Decentralized
Version
Control
System
9
Merging code into a central repository or integration
branch

10. Branching
Model
10

11. Git Flow
11

12. Github Flow
12

13. Other
Workflows
13

14. Build
System
14
Test, test coverage, static analysis, style checks

15. A W S
Code Build

16. Only Pay For
What You Use
16

17. Infrastructure As
Code
17

18. Defining
Codebuild
CloudFormation Resource
18
CodeBuildTest:
Type: AWS::CodeBuild::Project
Properties:
Name: !Sub "${EnvironmentName}-${AppName}-tests"
Description: !Sub "Run unit test for ${AppName}"
Artifacts:
Type: NO_ARTIFACTS
ServiceRole: !Ref CodeBuildDeploymentRole
Environment:
ComputeType: !Ref CodeBuildComputeType
EnvironmentVariables:
- Name: ENVIRONMENT_NAME
Value: !Ref EnvironmentName
- Name: BUCKET_NAME
Value: !Ref "ArtifactsBucket"
- Name: APP_NAME
Value: !Ref AppName
Image: !Ref CodeBuildDockerImage
Type: LINUX_CONTAINER
Source:
Type: GITHUB
Location: !Sub >
https://github.com/${GitHubOwner}/${GitHubRepo}.git
BuildSpec: "buildspec-test.yml"

19. Pull Request
19

20. Code
Reviews
+ + =
Github
Required
Checks
Merge

21. Enforce
Quality
Control
21
Unit test
Security validation
Code analysis
Linting

22. Branch
Protection
22

23. 23
True Story

24. Code Reviews
Foster a positive review culture
24

25. Accountability
25

26. Learn From One-Another
26

27. Improve Quality
27

28. C I Review
28Validate
Find bugs quicker
Code Test
Code reviews
Increase Quality
Consequence of continually validate
Merge Often
Generate the confidence in your process to be
able to merge often
More features

29. C D

30. What Is C D?
30
Definition according to AWS:
Continuous delivery is a DevOps software development practice where code changes are
automatically built, tested, and prepared for a release to production. It expands
upon continuous integration by deploying all code changes to a testing environment and/
or a production environment after the build stage. When continuous delivery is
implemented properly, developers will always have a deployment-ready build artifact that
has passed through a standardized test process. [12]

31. Continuous
Delivery
31
Source Code Changes
Build
Deploy To Testing Environment
Deploy To Production
<?PHP
!
Manual Approval

32. Continuous
Deployment
32
Source Code Changes
Build
Deploy To Testing Environment
Deploy To Production
<?PHP

33. Code Pipeline
33

34. Code
Pipeline
34

35. Build And
Package
35

36. Build
36
version: 0.2
phases:
build:
commands:
- echo Building package for production
- composer install --no-dev —optimize-autoloader
# …
post_build:
commands:
- echo Cleaning up!
- rm -rf docker test tests
artifacts:
files:
- ‘**/*'

37. 37
Delivery

38. Testing
38
03. Regression
Test performance degradation under maximum workload
04. Load Testing
Mimic real world use
DB usage
Network communication
Applications
01. End To End
Test combined functionality
How different pats of the system interact with each-other
Client/Server, Distributed systems
02. Integration
New code changes don’t impact existing functionality

39. Manual
Approval
39

40. Deployment
40

41. Deployment
Strategies
41
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/
using-features.rolling-version-deploy.html

42. Elastic Beanstalk
Deployment
Strategies [1 1]
42
Deployment Policy Load-Balanced Environments Single-Instance Environments
All at Once ✓ ✓
Rolling ✓ ☓
Rolling with an
Additional Batch
✓ ☓
Immutable ✓ ✓

43. Elastic Beanstalk
Deployment
Strategies [1 1]
43
Method Impact of Failed Deployment Deploy Time Zero Downtime No DNS
Change
Rollback
Process
Code
Deployed To
All at once Downtime Short ☓ ✓ Manual
Redeploy
Existing
instances
Rolling Single batch out of service; any successful
batches prior to failure running new
application version
Medium ✓ ✓ Manual
Redeploy
Existing
instances
Rolling with
additional batch
Minimal if first batch fails, otherwise, similar
to Rolling
Long ✓ ✓ Manual
Redeploy
New and
existing
instances
Immutable Minimal Very Long ✓ ✓ Terminate
New
Instances
New
instances

44. Elastic
Beanstalk
44

45. Create
Stacks
45
Application Stack Application Pipeline

46. 46

47. References
47
1.What is Continuous Integration? – Amazon Web Services
2.Introducing GitFlow
3.Understanding the GitHub flow · GitHub Guides
4.Configuring protected branches - User Documentation
5.About required status checks - User Documentation
6.Enabling required status checks - User Documentation
7.Git Workflow | Atlassian Git Tutorial
8.Enhanced Health Reporting and Monitoring - AWS Elastic Beanstalk
9.Enabling AWS Elastic Beanstalk Enhanced Health Reporting - AWS Elastic Beanstalk
10.Blue/Green Deployments with AWS Elastic Beanstalk - AWS Elastic Beanstalk
11.Deploying Applications to AWS Elastic Beanstalk Environments - AWS Elastic Beanstalk
12.What is Continuous Delivery? – Amazon Web Services