The document discusses implementing continuous integration for Android using tools like Jenkins alongside ticket systems and version control. It highlights the benefits of having readily available binaries and integrating unit tests, along with the configuration of jobs, build triggers, and post-build actions. Additionally, it mentions various plugins, including an Android emulator plugin, and provides an overview of the setup process.

1. Continuous Integration for Android
Raul Portales
@sla_shalafi

2. About Me

3. Continuous Integration
On top of:
Ticket System + Version Control

4. Why?

5. It's like having a flat data plan on your phone

6. Works on my machine

7. Binaries always ready

8. Integrate Unit Tests
(More on that later)

9. What?

11. There is a plugin for that.
But I need...

12. Plugins...

13. It even has a “Chuck Norris” plugin

14. Android Emulator plugin
More on that later

15. How?

16. Configuring Jobs
SCM & Build Triggers
Build Steps
Post-build Actions

17. Source Control
Jenkins integrates with almost every SCM
Even VSS

18. Build Triggers
Manual Trigger
On SCM change
Periodically
...

19. Build Actions
From shell to maven...
Also ant.

20. Post-Build Actions
Archive Artifacts
Notify on Failure
Run other Job

21. More nice stuff
Github Auth plugin

22. More nice stuff
Sonar Source

23. Installing Jenkins
Tomcat + jenkins.war

24. In fact, you don't even need tomcat

25. Jenkins and Android
Android Emulator plugin

26. What does it bring?
Special Build Steps
Manages emulators

27. Install Android prerequesites
Checks your projects for project.properties
Installs the required SDK versions

28. Create Android build files
Prepares your project to be built with ant

29. Demo time

30. Questions?