The default tooling for Android development (Android SDK along with its companion, the ADT plugin for Eclipse), provided by Google, is focused on providing ease of use to the developer; but what about the continuous integration (automatic build on commit, automatic execution of the units tests and integration tests, automatic analysis of the code quality, releasing, etc..) with tools such as Maven and Jenkins/Hudson ?
This talk will introduce the attendee to the Maven Android plugin, a nice alternative to the default ant tooling (and a great way to re use existing Maven artifacts), and to the Jenkins/Hudson continuous integration server, for Android development, focusing on the difficulty of executing an headless Android SDK.

Comments

Comments are closed.