This document discusses setting up continuous integration for Android projects using Jenkins. It recommends configuring Jenkins to run builds, tests, linting, and other analysis on code changes. Tests would include unit tests and monkey tests. Builds should support different configurations like debug and release. Plugins are available for Jenkins to support Android-specific tasks like running the emulator. The continuous integration system can be run on a master node and multiple slave nodes on different operating systems to test cross-platform compatibility.

1. Continuous Integration for Android
March 6th, 2013

2. What we want
Builds
Metrics
SCM Magic
Statistics
Reports

3. What we want
Builds
Metrics
SCM Magic
Statistics
Reports

4. Android build process

5. Android build process

6. Android build process

7. Additional routines
Different build types Testing
- Debug - Unit tests
- Release - Automatic black-box tests
- Monkey test
Documentation
- Javadoc Obfuscating
- ProGuard

8. Sources code analysis
- Lint
- FindBugs
- PMD
- Copy-paste detector
- CheckStyle

9. Builders

10. Builders

11. CI software

12. Jenkins

13. Jenkins plugins
- Android Lint Plugin
- Checkstyle Plugin
- PMD Plugin
- FindBugs Plugin
- Static Analysis Utilities
- Duplicate Code Scanner Plug-in
- Android Emulator Plugin
- ...

14. Android Emulator Plugin

15. Android Emulator Plugin

16. Android Emulator Plugin
Android monkey test: Succeeded after 500 events

17. Nodes
Master
(Linux)
Slave Slave Slave
(Linux) (Mac) (Windows)

18. Nodes
Android
Master
(Linux)
Slave Slave Slave
(Linux) (Mac) (Windows)
PHP, Java backends iOS .Net backends

19. About me
dnipro.gdg.org.ua
Alexey Ustenko
Android developer
bit.ly/AlexeyUstenko