Hi All,

The Android team has been working on resolving a travis build issue last week (and part of weekend) with travis-ci[1][2]. I has been testing with proting the build to cloudbees[3][4].

travis-ci:

In Travis the VM is running out of memory and getting killed. We fixed this by starting the emulator after compiling and I was able to make it pass 2 times[5][6], but when a PR[7] for AG was sent, we were back to the old problem[8] (travis-ci killed our build, because it's using a lot of memory)

CloudBees:

We are having trouble running the emulator[9] on CloudBees ([android] Emulator did not appear to start; giving up). We found a fix[10] but are not sure if we can apply it on CloudBees

[1] https://travis-ci.org/danielpassos/aerogear-android-security/builds

[2] https://travis-ci.org/secondsun/aerogear-android-security/builds

[3] https://aerogear.ci.cloudbees.com/job/aerogear-android-security

[4] https://aerogear.ci.cloudbees.com/job/aerogear-android-pipe

[5] https://travis-ci.org/danielpassos/aerogear-android-security/builds/43219446

[6] https://travis-ci.org/danielpassos/aerogear-android-security/builds/43256877

[7] https://github.com/aerogear/aerogear-android-security/pull/17

[8] https://travis-ci.org/aerogear/aerogear-android-security/builds/43295194

[9] https://aerogear.ci.cloudbees.com/job/aerogear-android-pipe/6/jdk=openjdk8/console

[10]: http://stackoverflow.com/questions/19349222/jenkins-android-emulator-emulator-did-not-appear-to-start-giving-up

-- Passos