CI/CD as first and last line of defence

CI/CD as first and last line of
defence
J I M M Y D A H L Q V I S T , S I G M A T E C H N O L O G Y C L O U D

Hello, I’m
JIMMY DAHLQVIST
Head of AWS Technology @ Sigma Technology Cloud
AWS APN Ambassador & Community Builder

@jimmydahlqvist
DevOps Trend
◦ Increased rate of change
◦ Micro services
◦ Automate everything
◦ Continuous integration / delivery

@jimmydahlqvist
What is DevOps?
?

“
DevOps empowers development teams
to own, run, and manage the end-to-
end delivery of an application or piece
of software. It eliminates the confusion
around ownership and drives teams
toward an automated, developer-
managed infrastructure.

@jimmydahlqvist
Micro Services
◦ Cloud Native Applications
◦ Breaking up the code
◦ Individual teams
◦ Scale and Release independently

@jimmydahlqvist
Micro Service Interaction
◦ Well-defined API
◦ Strong contracts
◦ Integration points increase
◦ Complexity grows
◦ Event / communication driven

@jimmydahlqvist
API test and Contract Test
◦ Producer driven
◦ Consumer driven
◦ Honor the contract

@jimmydahlqvist
INFRASTRUCTURE

@jimmydahlqvist
Infrastructure as code
◦ Single source of truth
◦ Model cloud infrastructure
◦ Version controlled
◦ Store everything in Git

@jimmydahlqvist
Except Secrets!
Never ever store secrets in
Git!

@jimmydahlqvist
Infrastructure verification
◦ Policy as code
◦ Linting
◦ Unit Testing

@jimmydahlqvist
IT’S AN ASYNCHROUNOUS WORLD

@jimmydahlqvist
Event driven systems
◦ Run code by reacting to events
◦ Several parts of the system can run
at the same time
◦ Match made in heaven for
serverless systems

@jimmydahlqvist
Serverless
◦ No servers to manage
◦ Execute code dynamically
◦ Scales automatically
◦ Pay for what we use
◦ AWS Lambda, Nano Service

@jimmydahlqvist
Continues Integration / Delivery

@jimmydahlqvist
CI/CD
◦ Repeatable reliable process
◦ Automate everything
◦ No human intervention
◦ Build in quality checks

@jimmydahlqvist
Temporary Environments
◦ Verify in the cloud
◦ Integration testing

@jimmydahlqvist
FIRST LINE OF DEFENCE

@jimmydahlqvist
PR-Testing Setup

@jimmydahlqvist
Pull Request Testing
◦ Run pipeline when PR is opened
◦ Find problems early
◦ Main branch always releasable

@jimmydahlqvist
Deploy it to Cloud
◦ Use temporary environments
◦ Full environment every time or use
name spaces / routing.

@jimmydahlqvist
Unit Test
◦ Test service internal functionality
◦ Run fast and in parallel

@jimmydahlqvist
Integration test
◦ Most important
◦ Verify all moving parts together
◦ Run it in the cloud
◦ Run fast or run limited scope

@jimmydahlqvist
API & Contract Test
◦ Honor the contract
◦ Focus on Contract tests

@jimmydahlqvist
Communicate Result
◦ Add test result to Pull-Request
◦ Prevent merge if tests are failing

@jimmydahlqvist
SECOND LINE OF DEFENCE

@jimmydahlqvist
Merged / Nightly Setup

@jimmydahlqvist
Merge Testing
◦ Run pipeline on merged changes
◦ “Integration” test
◦ Validate changes together
◦ Run in dedicated cloud
environment

@jimmydahlqvist
Run fast
◦ Don’t build up a merge queue
◦ Run fast or limited scope
◦ Bundle changes together

@jimmydahlqvist
Nightly Testing
◦ Possibility for extensive testing
◦ Run everything, speed doesn’t
matter
◦ Creates nightly releasable builds

@jimmydahlqvist
Communicate Result
◦ Integrate to communication tool
◦ Post test result every night

@jimmydahlqvist
Integration Test
◦ Run those heavy tests
◦ Don’t forget about asynchronous
integrations

@jimmydahlqvist
LET’S GO TO PRODUCTION

@jimmydahlqvist
Release Strategies
◦ Infrastructure
o In-Place
o Immutable
◦ Release process
o All at once
o Blue/Green
o Canary

@jimmydahlqvist
LAST LINE OF DEFENCE

@jimmydahlqvist
Deploy it!
◦ Production Environment
◦ Pick the correct strategy, business
driven.

@jimmydahlqvist
Blue / Green
◦ Provision a new environment, Green
◦ Shift all traffic at once to the Green
environment
◦ Keep Blue environment for fast
rollbacks

@jimmydahlqvist
Canary
◦ Form of Blue / Green deployment
◦ Shift a portion of traffic to the
Green environment
◦ Build confidence

@jimmydahlqvist
Smoke Testing
◦ Subset of unit and integration test
◦ Use real data!

@jimmydahlqvist
Monitor
◦ Monitor extensively after a deploy
◦ Use metrics to detect failed
deployments and problems

@jimmydahlqvist
Communicate & Rollback
◦ Both deploy started and smoke test
result
◦ If automatic rollback is started

@jimmydahlqvist
Roll it back
◦ Implement a rollback strategy
◦ Blue / Green makes it easy

@jimmydahlqvist
ONE MORE THING

@jimmydahlqvist
Chaos Engineering
What do you mean with you want to
break things in production?

“
Chaos Engineering is the discipline of
experimenting on a system in order to
build confidence in the system’s
capability to withstand turbulent
conditions in production.

@jimmydahlqvist
Chaos Engineering
◦ Not about breaking things
◦ Controlled experiments to inject
failures
◦ Find weaknesses in a system

@jimmydahlqvist
Testing in production
◦ Sounds risky?
◦ Data is different
◦ Abort if customers are affected

@jimmydahlqvist
Observability
◦ Understand status of a complex
system based on the system’s
outputs
◦ Business driven KPIs

Thank You!!
@jimmydahlqvist
https://www.linkedin.com/in/dahlqvistjimmy/
https://jimmydqv.com | https://dev.to/jimmydqv

CI/CD as first and last line of defence

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to CI/CD as first and last line of defence

Similar to CI/CD as first and last line of defence (20)

More from Jimmy Dahlqvist

More from Jimmy Dahlqvist (14)

Recently uploaded

Recently uploaded (20)

CI/CD as first and last line of defence

Editor's Notes