-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows
After updating the Android SDK installation, my Android Jenkins projects failed with the message "Emulator did not appear to start; giving up".
As it turned out, Android SDK tools r12 now contains two emulators, "emulator-arm.exe" and "emulator-x86.exe". The old "emulator.exe" just starts the real emulator process and then quits. So, when the android-emulator plugin checks the process, it is already dead.
As a workaround, I renamed emulator-arm.exe to emulator.exe, but of course it would be nice to have the emulator platform configurable in the plugin 
[JENKINS-10815] Emulator startup not detected with Android SDK tools r12
Good old Windows.
Due to a number of emulator bugs in r12 (as well as this change), my suggested workaround is to downgrade to SDK Tools r11.
But since this behaviour will be there in future, any suggestions as to a fix?
eifert
added a comment - Is the process check really necessary? The plugin waits for the adb port anyway...
Maybe the "report-console" argument could be (mis)used for startup detection? A detailed description is available with "emulator -help-report-console".
Other than that, the plugin could make the emulator binary name configurable, and directly start emulator-arm or emulator-x86.
eifert
added a comment - Is the process check really necessary? The plugin waits for the adb port anyway...
Maybe the " report-console" argument could be (mis )used for startup detection? A detailed description is available with "emulator -help-report-console".
Other than that, the plugin could make the emulator binary name configurable, and directly start emulator-arm or emulator-x86. Code changed in jenkins
User: Christopher Orr
Path:
src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
http://jenkins-ci.org/commit/android-emulator-plugin/6600e1d1f5e62f6ba6865d12324a78e6059d4d9b
Log:
[FIXED JENKINS-10815] Don't check whether emulator process is alive on Windows.
As you can see, I made the above change on a branch, jenkins-10815.
I don't have a free Windows 7 machine at the moment that I could install SDK r12 on, so if you have any comments or could test the attached build, that would be appreciated.
Richard Mortimer
added a comment - I did a quick check and it seems to work. Will check further later.
Richard Mortimer
added a comment - I did a quick check and it seems to work. Will check further later. eifert
added a comment - I tried it on Windows XP 32bit with SDK r12, startup seems to work fine now.
eifert
added a comment - I tried it on Windows XP 32bit with SDK r12, startup seems to work fine now. Thanks for testing; I've merged this and will probably do a release today or tomorrow.
Code changed in jenkins
User: Christopher Orr
Path:
src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
http://jenkins-ci.org/commit/android-emulator-plugin/6600e1d1f5e62f6ba6865d12324a78e6059d4d9b
Log:
[FIXED JENKINS-10815] Don't check whether emulator process is alive on Windows.
Integrated in 
plugins_android-emulator #6
[FIXED JENKINS-10815] Don't check whether emulator process is alive on Windows.
Christopher Orr :
Files :
- src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
Code changed in jenkins
User: Christopher Orr
Path:
src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
http://jenkins-ci.org/commit/android-emulator-plugin/6600e1d1f5e62f6ba6865d12324a78e6059d4d9b
Log:
[FIXED JENKINS-10815] Don't check whether emulator process is alive on Windows.
Good detective work! That is consistent with what I saw when I first starting trying to get a r12 emulator running on Windows 7. In the end I worked around the issue by using a r11 SDK environment that I had. I hadn't had time to investigate why it wasn't working and had assumed that it was just my environment but obviously it is not.