Permalink
Commits on May 23, 2016
  1. [FIXED JENKINS-35004] Disable console auth token at startup.

    Otherwise, by default starting with SDK Tools 25.1.6, you need to authenticate
    before you can start using the telnet interface.  So here we use the documented
    way of disabling this feature, i.e. returning to the old behaviour.
    orrc committed May 23, 2016
Commits on Apr 20, 2016
Commits on Apr 17, 2016
Commits on Apr 11, 2016
Commits on Apr 7, 2016
  1. Install SDK 24.4.1 by default.

    orrc committed Apr 7, 2016
Commits on Mar 28, 2016
  1. Add support for Android 6.0.

    orrc committed Mar 28, 2016
  2. Prevent emulators from using the new QEMU2 engine, which has missing …

    …features.
    
    The new emulator engine does not yet implement various command line flags that
    we need in order to detect that the emulator process has started, to set the
    emulator locale, and to set the emulator ports that we need.
    orrc committed Mar 28, 2016
  3. Ensure that emulator uses ports outside of the standard range.

    Otherwise, when multiple emulators — and thereby multiple ADB servers — run in
    parallel, then each of the ADB servers will race to register themselves with any
    new emulators that appear, rather than each ADB server only communicating with
    the one emulator it was intended for.
    
    See http://b.android.com/205197
    orrc committed Mar 28, 2016
  4. Remove the now-redundant connect and disconnect calls during startup.

    These were possible when using the localhost:XXXX style of connecting, and so
    are now no longer required.
    orrc committed Mar 26, 2016
  5. Fix the emulator port task so that it doesn't hang forever in case of…

    … failure.
    
    Previously, if the emulator failed to report its port, the build would end up in
    a state where it could never be aborted by the user.
    orrc committed Mar 26, 2016
Commits on Mar 26, 2016
  1. Ensure that the emulator ports used consist of an even port followed …

    …by an odd.
    
    When emulators are started without explicit ports, they take two consecutive
    ports, for the telnet and ADB interfaces, starting on an even number (5554).
    
    This isn't strictly required; the `-ports` emulator option will accept two
    non-consecutive ports, odd or even, and it will still work fine.  However, the
    new emulator engine seems to have killed off the `-ports` option, allowing only
    the more restrictive `-port` option, which requires an even port in the standard
    emulator port range.
    orrc committed Mar 26, 2016
Commits on Apr 9, 2015
  1. Merge pull request #49 from mKaloer/27707

    [FIXED JENKINS-27707] Removes -no-boot-anim flag.
    
    This was causing the plugin to prematurely declare emulators as fully started.
    orrc committed Apr 9, 2015
Commits on Mar 12, 2015
  1. Add support for Android 5.1.

    orrc committed Mar 12, 2015
Commits on Feb 13, 2015
  1. Revert "[JENKINS-11952] Remove redundant (dis)connect calls while wai…

    …ting for startup."
    
    This reverts commit f2fcd2f.
    
    This is required as, per the previous commit, we're using the "localhost" style
    of emulator connection string once again.
    orrc committed Feb 13, 2015
  2. [JENKINS-11952] Return to the "localhost:XXXX" style of connecting to…

    … emulators.
    
    For some reason, connecting to the emulator in this manner appears to be
    somwehat more reliable than connecting with the regular "emulator-XXXX" style.
    
    From the various JIRA issues opened against the most recent plugin releases,
    this instability seems to affect Mac OS X more than other operating systems.
    
    Now we use "localhost:XXXX", while sticking to a four-digit port number, as some
    tools seem to assume that the emulator port is always four-digits.
    
    While it's still a problem that ddmlib — as used by tools like the Maven Android
    plugin — only recognise emulators with the "emulator-XXXX" scheme, this should
    not be a problem, as the emulator itself at startup registers with adb in this
    style.  While this means that running "adb devices" may show two connected
    devices (e.g. "emulator-5554" and "localhost:5555"), libraries like ddmlib will
    use the "emulator" variant, while build steps that call `adb` will automatically
    read the ANDROID_SERIAL environment vairable and use the "localhost" variant.
    orrc committed Feb 13, 2015
  3. Attempt to (un)install APK even if waiting for the core process timed…

    … out.
    
    This fixes the behaviour to match what the log output claims is happening.
    orrc committed Feb 13, 2015
Commits on Feb 12, 2015
  1. Also send stderr to the build log for various commands we need to run.

    Sometimes we get bug reports where there's likely error information missing
    since we were not capturing stderr.
    orrc committed Feb 12, 2015