Continuous Integration from Ground to Cloud discusses the challenges of CI and how moving to cloud-based CI can help address them. The document outlines challenges such as people resisting change, slow builds, and lack of testing. It then provides solutions like demonstrating benefits, optimizing code and builds, and starting with smoke tests. Moving CI to the cloud can improve resource utilization, reduce maintenance overhead, and make parallel and multiple environment builds and tests easier. Some concerns are potential speed issues, technical constraints, and security policy conflicts.

1. Continuous Integration
From Ground To Cloud
Juven Xu 许晓斌

2. Father, Programmer, Trainer, Coacher, and Author
@juvenxu

3. I’m going to talk
1. Challenges of CI, and possible solutions.
2. What is CI in Cloud, and what we can benefit from it.

5. Essential
Fast Feedback
High Quality

6. Challenges
1. People don’t want to change
2. Slow build
3. No/little tests
4. Communication gap between dev team and CI

7. People Don’t Want To Change
Find their pain point
Demonstrate the new idea
Support from management level

9. Slow Build
1. Optimize your machine
2. Optimize your code
3. Optimize your build

10. Optimize Your Build
Build Stages
Dedicated Build Farm
Parallel Build
Incremental Build
In Memory Build

12. No/Little Tests
1. Start with smoke test (best ROI)
2. Introduce TDD/ATDD
3. Use metrics to encourage people
4. Support from management level

13. Communication Gap
between dev and CI team
Eat your own dog food
CI as a service

14. Where Is the Cloud?

15. Cloud Computing In a Nutshell
SaaS / PaaS / IaaS
Public / Private Cloud
CI in Cloud

16. Benefits of CI in Cloud
Improve Resource Utilization
Reduce Maintenance Overhead

17. Benefits of CI in Cloud
Multiple build environment is easy
Parallel build is easy
Multiple test environment is easy

18. Benefits of CI in Cloud
No communication gap between dev
and CI team

19. travis-ci.org

21. &

22. Concerns of CI in Cloud
It might be slower
It might have technical constraints
It might not conform to your security policy

23. Q&A
@juvenxu