isabella232 / android-sdk-installer

Android SDK Installer Script (Do not delete, this is used by appium CI)

Android SDK Installer

Installer script for the Android SDK. Designed to simplify automated setup of CI environments.

Usage

curl -L https://raw.github.com/embarkmobile/android-sdk-installer/version-1/android-sdk-installer | bash /dev/stdin --install=build-tools-18.1.0,android-17,sysimg-17 && source ~/.android-sdk-installer/env

The above command will download and install the SDK in $HOME/.android-sdk-installer. You can override it with --dir=custom_path.

You can specify components to install directly with --install=component1,component2,.... The is the same as installing it with:

android update sdk --no-ui -a --filter component1,component2,...

platform-tools is automatically installed. Some typical filters:

build-tools-18.1.0,android-17,sysimg-17,extra-android-support,extra-google-google_play_services,extra-google-m2repository,extra-android-m2repository

To get a full list of available SDK components, run:

android list sdk --extended -a

Currently the script is optimized to be run in a clean environment, and does not efficiently update an existing environment (it may download and install existing components again).

You may also include the script directly in your project, but then it will not be updated to handle newer Android SDK releases.

Emulator

The script also downloads and installs the wait_for_emulator script, which can be used to wait until the emulator has started.

Typical usage:

echo no | android create avd --force -n test -t android-17 --abi armeabi-v7a
emulator -avd test -no-skin -no-audio -no-window &
wait_for_emulator

Operating System Notes

Ubuntu

You may need to install the following first:

sudo apt-get install -qq libstdc++6:i386 lib32z1

Mac

Supported, thanks to a contribution by sebv.

Windows

Will probably not be supported.

Backwards Compatibility

For CI environments it is important that the same setup script continue working over time. Therefore an effort will be made to:

1. Keep the script always stable and working as documented below.
2. Keep the script working as far as possible with newer Android SDK versions, without breaking existing builds.

We assume for example that newer versions of for example platform-tools will remain backwards compatible, but that a specific version of build-tools and specific Android versions may be required.

If the API / usage pattern of this script is ever changed, it will be released under a new URL (new branch), and the old version will conitnue running as before. You should always use a version from a specific version branch, and not directly from master.

Sample Travis CI Configuration

This assumes that the new Gradle-based Android build system is used, with the Gradle wrapper.

language: java
jdk: oraclejdk7
before_install:
    # Install base Android SDK and components
    - sudo apt-get install -qq libstdc++6:i386 lib32z1
    - export COMPONENTS=build-tools-18.1.0,android-17,sysimg-17,extra-android-support,extra-google-google_play_services,extra-google-gcm,build-tools-18.1.0,extra-google-m2repository,extra-android-m2repository
    - curl -L https://raw.github.com/embarkmobile/android-sdk-installer/version-1/android-sdk-installer | bash /dev/stdin --install=$COMPONENTS
    - source ~/.android-sdk-installer/env

    # Create and start emulator
    - echo no | android create avd --force -n test -t android-17 --abi armeabi-v7a
    - emulator -avd test -no-skin -no-audio -no-window &

install:
    # Without TERM=dumb, we get mangled output in the Travis console
    - TERM=dumb ./gradlew assemble

before_script:
    # Make sure the emulator has started before running tests
    - wait_for_emulator

script:
    - TERM=dumb ./gradlew test connectedCheck

More Travis CI examples

• Robospice - Testing on multiple emulators in parallel, using Maven
• ZXing Android Minimal - Building both an apklib with Maven, and aar with Gradle (no tests)

License

Unless indicated otherwise, files in this project are under the MIT license.

When using / adapting these scripts in your own projects, I only ask that you keep the copyright headers, including the link back to this project.