continuous integration for androids
DESCRIPTION
TRANSCRIPT
- 1. Continuous Integration of androids Kirill Zotin 19.12.2012
- 2. Continuous integration 1 click build Every commit is built and tested Fast feedback Static code analysis 1st step to Continuous Deployment
- 3. Build process
- 4. Ant Make for Java Imperative (tell how to compile, run tests, package) No lifecycle support No conventions Easy to extend
- 5. Declarative (describe result) Default conventions, lifecycles, archetypes Dependencies management! Repositories! More difficult :(
- 6. Limitations Dependency management IDE integration Different builds of same project (Prod/test, proguard on/off, multiple apks) Maven: Artifacts pushed to Remotes with delays
- 7. The best of 2 worlds! Power and flexibility of ANT Dependency management and conventions of Maven Groovy DSL
- 8. gradle-android-pluginGoal - easy to: Reuse code and resources Create several variants of an application, either for multi-apk distribution or for different flavors of an application Extend and configure the build
- 9. gradle-android-pluginCurrent limitations: No IDE integration No support for Renderscript No support of NDK No support for Proguard No Lint integration Etc...
- 10. gradle-android-pluginProduct Flavors + Build Types = Build variants
- 11. Demo time!
- 12. Distribute Email Dropbox / Drive TestFlight / Launchpad / ... Repository managers (Nexus, Archiva)
- 13. Thanks! Questions? Suggestions? ;)http://bit.ly/gdgdnipro