[JIRA] (JENKINS-11973) AVD should be in workspace instead of system-global

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon commented on JENKINS-11973 AVD should be in workspace instead of system-global Code changed in jenkins User: Jørgen P. Tjernø Path: .gitignore src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java src/main/java/hudson/plugins/android_emulator/AndroidEmulatorContext.java src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java src/main/java/hudson/plugins/android_emulator/SdkInstaller.java src/main/java/hudson/plugins/android_emulator/TaskDispatcher.java src/main/java/hudson/plugins/android_emulator/builder/AbstractBuilder.java src/main/java/hudson/plugins/android_emulator/sdk/AndroidSdk.java src/main/java/hudson/plugins/android_emulator/util/Utils.java src/main/resources/hudson/plugins/android_emulator/AndroidEmulator/config.jelly src/main/resources/hudson/plugins/android_emulator/AndroidEmulator/global.jelly src/main/webapp/help-keepInWorkspace.html http://jenkins-ci.org/commit/android-emulator-plugin/430606da6fef941288b5f427a696a5b8dcdb7c13 Log: JENKINS-11973 Option for emulators in $WORKSPACE This adds a global option that essentially does ANDROID_SDK_HOME=$WORKSPACE, causing emulators to be put into $WORKSPACE/.android. This allows you to run concurrent jobs on the same slave, and to run the same emulator config from two different jobs on the same slave. It also makes the emulators more isolated and allows you to clean-slate the emulators by wiping out the workspace.

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