Add Travis CI builds for PRs?

[barbeau]

IMHO adding Travis CI support to this project would be helpful - it would help reveal issues like #187 immediately, rather than having to track down their cause later.

@broady @markmcd Thoughts?

If you're willing to turn on Travis support for this project in the Travis CI console, I'd be willing to try configure the .travis.yml script. I've done this on many Android apps, but never on a library before, and its always good to learn new things :).

[markmcd]

I've started on this in #203 but there's a test that's failing only in Travis that I haven't had a chance to look at. If you're keen to look at that then we'd be set :D

You can also fork the repo and enable Travis for your fork while you develop, which is what I did.

[barbeau]

@markmcd Thanks, didn't know you could enable Travis on forks. I'll see if I can take a look.

[barbeau]

So I think the issue is that you need to run the Google APIs emulator image on Travis to access Google Play Services. The names of these images also changed earlier this year - see my post on SO here:
http://stackoverflow.com/questions/28751111/invalid-abi-armeabi-v7a-for-the-selected-target-with-google-apis-21/28751112#28751112

I just pushed an attempt to fix this in this branch:
https://github.com/barbeau/android-maps-utils/tree/travis2

We'll see what happens...

[barbeau]

Well, no luck this time - the emulator startup is timing out. This should be close, though. I'll see if I can do trial-and-error a bit more...

[barbeau]

So I have a working version of API 21 with the Google API emulator here:
https://github.com/OneBusAway/onebusaway-android/blob/master/.travis.yml

I'm going to see if I can get a version of this working with API 23.

[barbeau]

Here's the latest branch I'm working on:
https://github.com/barbeau/android-maps-utils/tree/travis3

This has the Google API emulator starting and the build executing - see this Travis build. However, it fails with:

:library:connectedDebugAndroidTest FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':library:connectedDebugAndroidTest'.
> com.android.builder.testing.api.TestException: com.android.builder.testing.api.DeviceException: com.android.ddmlib.ShellCommandUnresponsiveException

Usually this means ADB timed out:
http://stackoverflow.com/a/28949723/937715

The fix for this is normally to increase ADB timeout via the Travis variable ADB_INSTALL_TIMEOUT.

However, I've bumped it up to 15 min so far and I'm still getting the same exception on Travis.

Also, not sure if its related to these issues, but I did find this open AOSP issue saying that Google Play Services is broken on the Google API emulator starting with API Level 22. It's been triaged but is still open, so the same issue may exist on API Level 23 emulator.

[barbeau]

I'm starting to wonder if this is an emulator issue - I spun up the Google APIs ARM (armeabi-v7a) emulator on my work machine, and it took > 10 min. And, I got the same com.android.ddmlib.ShellCommandUnresponsiveException when trying to run the tests from the command line, even after the emulator had fully booted.

When I ran the tests from Android Studio, they were very slow (240s total) - I also saw this while they were running:

However, given enough time, the tests did eventually pass when run from Android Studio. If it takes this long on my work machine, Travis is going to be far longer than that, so the slowness is certainly contributing to the problem. I wonder if the API Level 23 Google API emulator takes longer to boot than the past versions.

There still seems to be something else going on, though - I then went back and tried to run the tests from the command line again - and again I got com.android.ddmlib.ShellCommandUnresponsiveException.

@markmcd @broady Do you know if anything changed with API Level 23 Google API emulator that would prevent Gradle from installing/running from the command-line with ./gradlew connectedDebugAndroidTest?

[broady]

I'm not sure. It would be very bad if the Android team broke that.

@jfschmakeit any thoughts/knowledge?

[barbeau]

Also, looks like gradlew installDebug from command line fails for the demo app, with the same com.android.ddmlib.ShellCommandUnresponsiveException. I can, however, install/run it from Android Studio without a problem, and uninstall it via adb uninstall com.google.maps.android.utils.demo from the command line.

[barbeau]

Yeah, seems something is up with the API 23 Google API emulator image.

I finally (!) got a successful Travis build (I was missing one piece - compileSdkVersion has to be Google APIs too):
https://travis-ci.org/barbeau/android-maps-utils/builds/83234555

...but I had to revert back to API 21 Google APIs emulator image. The exact same setup on API 23 Google APIs image fails (on Travis and locally) with the com.android.ddmlib.ShellCommandUnresponsiveException error:
https://travis-ci.org/barbeau/android-maps-utils/builds/83233500

Here's the commit that's the difference between the two versions:
barbeau@a5eecd7

Unless I'm missing something, until the issue with the API 23 Google API emulator is resolved, our only option for running tests on Travis CI would be to revert the project to using compileSdkVersion "Google Inc.:Google APIs:21".

@markmcd @broady Thoughts? If that works for you I can see if I can trim down the .travis.yml a bit to match @markmcd's original work, and open a PR.