|
|
_0.png) |
|
|
|
|
Issue Type:
|
 Bug
|
|
Assignee:
|
Christopher Orr
|
|
Components:
|
android-emulator |
|
Created:
|
09/Aug/12 12:09 AM
|
|
Description:
|
If we create two emulators for the same platform, but with different ABIs, the plugin won't realise that a new emulator needs to be created.
e.g. a job using an Android 4.1 AVD with x86 ABI will use the name "hudson_en-US_240_WVGA_android-16".
Creating another job with Android 4.1, but with the ARM ABI will check for an emulator also called "hudson_en-US_240_WVGA_android-16", find that it exists and won't create it.
Ideally, the ABI name (if any) should be part of the generated AVD name.
|
|
Project:
|
Jenkins
|
|
Priority:
|
 Minor
|
|
Reporter:
|
Christopher Orr
|
|
|
|
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
|
|
Locked
Code changed in jenkins
User: Christopher Orr
Path:
src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java
src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java
src/main/resources/hudson/plugins/android_emulator/Messages.properties
src/main/webapp/help-targetAbi.html
http://jenkins-ci.org/commit/android-emulator-plugin/0c1f816134b3121c7b8f01f52ef413019a2946a2
Log:
[FIXED JENKINS-14740] Include ABI in generated AVD name.
Also expand variables in the 'Target ABI' field at runtime.
Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/dcd9999ab390...0c1f816134b3