Continuous Delivery on Android with Travis
Description:
This is a continuous delivery example with an Android application using gradle as the build system and dependency manager, Robospice for asynchronous networking inside the Android app, Instrumentation framework for functional testing, Support Library v4 and v7 for compatibility, Travis as the continuous integration server and TestFlight as the deployment service. You can find the detail setup and explanations for all these in my blog.
Travis CI Status
Scenario:
This example shows you how to configure an Android application with two product flavors (free and paid) taking advantage of the new build system to use different assets for each application, implement different features through build config injection and test and deploy each app individualy with Travis and TestFlight. I found this especially useful when you are on a project with a large team divided and each part is developing/testing different features on the same application.
Building and Testing:
In order to build and test the application, clone this repo:
$ git clone git@github.com:Ruenzuo/android-cd-travis-example.gitThen execute the tests with the gradle wrapper, you will need some device or emulator connected to adb before:
$ cd android-cd-travis-example && chmod +x gradlew && ./gradlew connectedInstrumentTest
For more information on how to get started with each tool/framework, go to:
gradle
Robospice
Instrumentation
Support Library
Travis
TestFlight
To-Do
[✓]Make it public.[✓]Write the blog post. It's here.[ ]Write better tests. Currently I'm doing some ugly workarounds for testing ads, I'm accepting suggestions on this :)
License
The MIT License (MIT)
Copyright (c) 2014 Renzo Crisóstomo
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.