Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: android-emulator-plugin
-
Labels:None
-
Environment:Windows
-
Similar Issues:
Description
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 
Attachments
Activity
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
Version 1.18 has now been released, which includes this update.
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.
Thanks for testing; I've merged this and will probably do a release today or tomorrow.