Join FlipAndroid.COM Telegram Group: https://t.me/joinchat/F_aqThGkhwcLzmI49vKAiw


Android Emulator Plugin en Jenkins – ¿Cómo extender el tiempo de espera?

He logrado obtener la configuración del complemento de Android Emulator y trabajar en Jenkins. Sin embargo, mi problema es que se agota después de 3 minutos. Lo estoy funcionando solamente en una caja muy lenta del nettop Linux (átomo de la inteligencia) así que imagino que tomará MUCHO más largo para comenzar el emulador.

¿Hay una manera de extender el tiempo de espera? Parece que el emulador está empezando; Para las primeras encuestas, su informó como fuera de línea, entonces no.

Mi salida de la 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 

  • Trabajo de Jenkins usando Gradle no puede encontrar ejecutable
  • Emulador de Android en Jenkins error: dispositivo desconectado
  • Android ZBar Excepción sólo con Jenkins construir
  • Cómo utilizar la tarea deviceCheck para ejecutar pruebas en dispositivos remotos
  • TestUI (Jenkins) utilizando espresso
  • Incrementa el número de compilación de Android en Integración continua
  • ConnectedAndroidTest en varios emuladores
  • Pruebas de unidad de Android con Jenkins en una máquina sin cabeza
  • 2 Solutions collect form web for “Android Emulator Plugin en Jenkins – ¿Cómo extender el tiempo de espera?”

    ¿Qué versión del sistema operativo Android está intentando utilizar?

    Si está usando algo superior a Android 2.2 o 2.3.3, recomendaría cambiar la versión de su sistema operativo Android a estos, ya que arrancan mucho más rápido.

    Además, si hace clic en el botón Avanzado situado debajo del encabezado "Opciones comunes de emulador" en la página de configuración de Jenkins, podría intentar jugar con la configuración de un retraso de inicio. Esto podría ayudar si su compilación requiere una gran cantidad de procesamiento antes de utilizar el emulador para cualquier cosa.

    Disculpas por el híbrido Respuesta / Comentario, me gustaría haber comentado si tenía el representante.

    Solución: Utilice un dispositivo de hardware.

    FlipAndroid es un fan de Google para Android, Todo sobre Android Phones, Android Wear, Android Dev y Aplicaciones para Android Aplicaciones.