|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Code changed in jenkins
User: Christopher Orr
Path:
src/main/java/hudson/plugins/android_emulator/AndroidEmulatorContext.java
http://jenkins-ci.org/commit/android-emulator-plugin/7949052acba9181ede1ecfed630b0059f113e9de
Log:
JENKINS-11952 Return to the "localhost:XXXX" style of connecting to emulators.
For some reason, connecting to the emulator in this manner appears to be
somwehat more reliable than connecting with the regular "emulator-XXXX" style.
From the various JIRA issues opened against the most recent plugin releases,
this instability seems to affect Mac OS X more than other operating systems.
Now we use "localhost:XXXX", while sticking to a four-digit port number, as some
tools seem to assume that the emulator port is always four-digits.
While it's still a problem that ddmlib — as used by tools like the Maven Android
plugin — only recognise emulators with the "emulator-XXXX" scheme, this should
not be a problem, as the emulator itself at startup registers with adb in this
style. While this means that running "adb devices" may show two connected
devices (e.g. "emulator-5554" and "localhost:5555"), libraries like ddmlib will
use the "emulator" variant, while build steps that call `adb` will automatically
read the ANDROID_SERIAL environment vairable and use the "localhost" variant.