As part of the Tikal internal DevOps course, this is the session about CI

1. Tikal DevOps courseYoram Michaeli
Continuous Integration
Introduction
CI

2. • Everything as code
• Similarity of environments
• Developers operations
• Operation development
• Continuous <xxx>
• Automation
DevOps key concepts

3. You’re not
alone

4. You’re not alone...
● This is not a one-man-show!
● Agile processes
● Shift-left approach
● Time-to-market
● On-going integration

5. Continuous Integration

6. Continuous Integration is...
“Continuous Integration is a software development practice
where members of a team integrate their work frequently,
usually each person integrates at least daily - leading to multiple
integrations per day.
Each integration is verified by an automated build (including
test) to detect integration errors as quickly as possible.”
Martin Fowler

7. Continuous Integration key concepts
● Integrate early
● Integrate often
● Fail fast and bring the pain forward
● Feedback loops - the tension between speed and quality
○ Per-commit — fast iteration
○ Nightly - qualified and reasonable iteration
○ Weekly - high quality and slow iteration

8. Developer
Aspect

9. Developer aspect
● ‘It works for me!’
● Isolated build and test environment
● Simple work procedures
● Clear failures notifications
● Simple code integration

10. QA Aspect

11. QA aspect
● Frequent versions
● Unit tests
● Regression tests
● Integration tests
● Automation

12. Team
Aspect

13. Team aspect
● Time-to-market
● Clear status
● Reduce release errors
● Production-like environment
● Shift-left

14. Basic CI Flow

15. Basic CI flow
● Code commit
● Code build
● Unit tests
● Deployment
● Integration tests
● Notification for each step failure

16. Effective CI

17. Effective CI - the 5 minutes rule
An effective CI is - following a code change, a
no-more-than-5-minutes-build is being
triggered, so that a code build, alongside a
validation test-set, is done and - at the end of
the process - there is a notification whether the
change caused a failure or not with a proper
blame indication

18. CI ➢ Pipeline

19. CI ➢ PIPELINE
● Once you have CI (and even CD) in place, the deployable
unit path is called a pipeline
● A pipeline procedure is triggered when code is committed.
Next, the build system compiles the code and runs unit
tests.
● After integration testing is done, you can create images
and push them to a registry service.

20. CI tools

21. CI tools
Jenkins
TeamCity
Travis-CI
Bamboo
GitLab-CI
CircleCI
Codeship
GO CD
Amazon Pipeline