Jenkins: Emulator UI doesn't appear when running on Windows 7

上一篇 / 下一篇  2013-10-11 18:01:19 / 个人分类:jenkins

Building in workspace C:\Program Files (x86)\Jenkins\workspace\test
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/tools/android.bat list target
[android] Using Android SDK: D:\tools\android\android-sdk_r18-windows\android-sdk-windows
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe start-server
[android] Starting Android emulator
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/tools/emulator.exe -no-boot-anim -ports 40790,40791 -avd AVD -no-snapshot-load -no-snapshot-save
Failed to create Context 0x3005
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
* daemon not running. starting it now on port 40792 *
* daemon started successfully *
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe connect localhost:40791
[android] Waiting for emulator to finish booting...
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 shell getprop dev.bootcomplete
error: device offline
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe connect localhost:40791
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 shell getprop dev.bootcomplete
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe connect localhost:40791
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 shell getprop dev.bootcomplete
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe disconnect localhost:40791
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe connect localhost:40791
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 shell getprop dev.bootcomplete
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 logcat -v time
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe connect localhost:40791
[android] Attempting to unlock emulator screen
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 shell input keyevent 82
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe -s localhost:40791 shell input keyevent 4
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe connect localhost:40791
[android] Emulator is ready for use (took 51 seconds)
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe disconnect localhost:40791
[android] Stopping Android emulator
[android] Archiving emulator log
$ D:\tools\android\android-sdk_r18-windows\android-sdk-windows/platform-tools/adb.exe kill-server
Finished: SUCCESS


Solved:

Emulator UI doesn't appear when running on Windows 7

If running Jenkins as a service on Windows 7 or newer, you may find that while the plugin can start an emulator, its user interface may not appear, even if configured to do so. 
This is due to something called Session 0 Isolation, which prevents services from starting UIs for security reasons.

If you really need to see the emulator UI, you can either run Jenkins not as a service, or add a slave node to Jenkins (e.g. launch slave via JNLP on the same machine) which will bypass this isolation.


https://wiki.jenkins-ci.org/display/JENKINS/Android+Emulator+Plugin#AndroidEmulatorPlugin-Knownissues


TAG:

 

评分:0

我来说两句

Open Toolbar