Introduction to Continuous Integration

1. Continuous Integration with
Jenkins

2. Goals
Push code
Push code
Review code
Build on push
Daily build
Test on push
Nightly regression
Performance testing

3. About Trainer

4. Introduce Yourself
2 minutes

5. What is your
Continuous Integration ?

6. What is your CI system ?
No
Build Server
Nightly
Build
Automated
Build
with
Basic
Automated Test
Use
Metrics
More
About Testing
Automated
Acceptance
Testing
Continuous
Deployment
Continuous
Delivery

8. Stressful Releases

10. What is CI ?
• Continuous Integration !!!
• Automated Everything
• Build as often as possible
• Build early and often
• e.g. On every commit/nightly build

11. What is CI ?
• Not just technical
• Organization and culture

12. What is CI ?
• Software development practice
• What people do, not about what tools
• Integrate frequently
• Fast feedback

13. Benefit of CI
• Fewer error/Reduce risks
• Fast feedback
• Much less manual testing
• Regression test without additional effort
• Generate deployable software
• Great confidence in the product

14. อะไรที่ไม่ใ๡่ CI
• Nightly build
• Developer branch
• Scheduling integration point
• Building via IDE

16. CI Practices
1. Maintain a single source repository
2. Automate the build
3. Make your build self-test
4. Everyone commit to the mainline everyday
5. Every commit should build the mainline on integration machine
6. Keep the build fact
7. Test in a clone of the production environment
8. Make it easy for everyone to get the latest executable
9. Everyone can see what is happen
10.Automate deployment

17. Single Source Repository
• Single point of truth
• Everyone’s code in the same place
• NOT a branch per developer
• Shared ownership

18. Automate Build
• IDE is not automating !!
• Use build tool
• Compile, package and test

19. Self-testing Build
• Direct from source to running build
• No manual copy
• No click
• No edit config file

20. Self-testing Build
• Test with
• Unit tests
• Functional tests
• Performance tests

21. Self-testing Build
• Responsible persons should be notified when
anything fails
• Test web in more browser

22. Commit More Often
• At lease one per hour
• Need small unit of work
• To commit cleanly you need to update first

23. Every Commit Build
• It’s all about fast feedback
• Small changes
• Less to merge or fix

24. Publish Latest Distributable
• Make it easy to get final product
• Should only build once
• Configuration is separate

25. Test in Production Clone
• Detect multi-thread, cluster, load balance issue
• Test system architecture
• Real database

26. Keep Build Fast
• It’s all about feedback
• If thing break you find out about it, fresh in your mind
• Keep up with frequent commit

27. Everyone See What’s Happening
• Reduce time to fix
• No excuse to commit on broken build
• It’s not about blame, it about feedback

28. Automate Deployment
• Reduce human error
• Verify can run on somewhere other than “My Machine”
• Test not only on code, but deployment process too
• Don’t tie up System Administrators with boring stuff
• Don’t tie up Developers waiting for feedback

29. Make CI Work
• Can not done in isolation
• Pick the right tool for the right job
• It’s not silver bullet

30. Build Pipeline

31. Traditional CI Flow

32. Build Pipeline Flow

33. One Click Deploys
• Require the Build pipelines
• Reduce deployment time and risk
• Make go live a non-event

34. History

35. Summary
• CI and Build pipeline improve
• Quality
• Time to market
• Confidence
• Continuous Deployment/Delivery is the next step
• Require Developers and System Administrator to work
closely together

36. 3 persons/group

37. Your
Build Pipeline
?

38. Build/Deployment Pipeline
1. Clean 2. Checkout
3. Download
Library
4. Compile
5. Package 6. Setup DB 7. Run Test 8. Deploy

39. How to Self-Testing ?

40. What is Jenkins ?
• Continuous Integration Server
• Opensource
• A lot of useful plugin
• Well document
• Active community

41. Goals
Push code
Push code
Review code
Build on push
Daily build
Test on push
Nightly regression
Performance testing

42. Let’s Go !!!