CI/CD pipelines

Alexandra Calota

Use a real story, live the story, be the story

 WHAT WE’LL TALK ABOUT

1 2 3

OVERVIEW INDUSTRY BEST PRACTICES PERSONAL EXPERIENCE

OVERVIEW
Developing across different time zones
 DIFFICULTIES

Real-time communication Meetings

Sense of belonging Syncing

 DEVELOPMENT TIMELINE

STEP 1 STEP 2 STEP 3 STEP 4

SOURCE BUILD TEST PRODUCTION

CONTINUOUS INTEGRATION

CONTINUOUS DEPLOYMENT
INDUSTRY BEST
PRACTICES
 CONTINUOUS INTEGRATION GOALS

Automatically kick off a Build and test in a

new release consistent environment

Have an artifact ready Close feedback

for deployment loop
Continuous integration best practices

● Create pipelines that enable rapid iteration

○ Rapid and full pipelines

● Test your container images

● Establish security early in pipelines

○ Request review
○ Linting and static code analysis
○ Scan for vulnerabilities
 CONTINUOUS DEPLOYMENT GOALS

Automatically deploy to Deploy to prod safely, Deliver faster

staging for testing without affecting customers
Continuous deployment best practices

● Use GitOps methodology

● Promote, rather than rebuild container images

● Use more advanced deployment and testing patterns

○ Separate clusters for different environments
○ Keep pre-production environments close to production

● Prepare for failures in production

PERSONAL
EXPERIENCE
Dedicated CI/CD Dedicated development
pipeline team productivity sub-team

Team effort for the CI/CD ?

pipeline
CONCLUSIONS
 EFFECTS OF CI/CD

FROM TO

Deployment frequency weekly - monthly hourly - daily

Change lead time one - six months one - seven days

Change failure rate 46 - 60% 0 - 15%

 48% of
software teams
Thank you!