android jenkins android-emulator-plugin

Complemento Android Emulator en Jenkins-¿Cómo extender el tiempo de espera?



android-emulator-plugin (2)

¿Qué versión del sistema operativo Android estás tratando de usar?

Si está utilizando algo superior a Android 2.2 o 2.3.3, le recomendaría cambiar su versión del sistema operativo Android a estos porque se inician mucho más rápido.

Además, si hace clic en el botón Avanzado ... ubicado debajo del encabezado "Opciones comunes del emulador" en la página de configuración de Jenkins, puede intentar jugar con la configuración de un retraso de Inicio. Esto podría ayudar si su compilación requiere mucho procesamiento antes de usar realmente el emulador para nada.

Disculpas por la respuesta / comentario híbrido, solo habría comentado si tuviera el representante.

Logré obtener la configuración del complemento Android Emulator y trabajar en Jenkins. Sin embargo, mi problema es que se agota después de 3 minutos. Solo lo estoy ejecutando en un Linux nettop muy lento (Intel Atom) así que imagino que tomará MUCHO más tiempo iniciar el emulador.

¿Hay alguna manera de extender el tiempo de espera? Parece que el emulador está comenzando; Para las primeras encuestas, se informó como fuera de línea, luego no.

La salida de mi consola está abajo.

Gracias

Started by user Si Pickles [EnvInject] - Loading node environment variables. Building in workspace /var/lib/jenkins/jobs/mycompany_myapp/workspace Updating svn://localhost/mycompany/code/trunk/myappProject at revision ''2013-08-11T23:03:06.957 +0100'' At revision 98 no change for svn://localhost/mycompany/code/trunk/myappProject since the previous build $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator $ /var/lib/jenkins/tools/android-sdk/tools/emulator -no-boot-anim -ports 48437,50001 -avd google17 -no-snapshot-load -no-snapshot-save -no-window -no-audio * daemon not running. starting it now on port 51447 * * daemon started successfully * Failed to Initialize backend EGL display $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:50001 shell getprop dev.bootcomplete $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:50001 [android] Timed-out after waiting 180 seconds for emulator $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:50001 [android] Stopping Android emulator emulator: WARNING: Could not initialize OpenglES emulation, using software renderer. $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb kill-server Archiving artifacts Finished: NOT_BUILT


Solución: use un dispositivo de hardware.