|
|
_0.png) |
|
|
|
|
Issue Type:
|
Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Christopher Orr
|
|
Components:
|
android-emulator |
|
Created:
|
14/Jun/12 4:24 AM
|
|
Description:
|
The plugin will automatically install the Android SDK if it isn't already installed on the slave. However, when new versions of the Android SDK and new APIs come out, they aren't automatically installed - so any build that attempts to use them will fail.
For example, the plugin automatically installed the Android SDK, and at that time, the latest Android API was 14. Recently, a new project started, and it targetted SDK 15. The build failed for this project with this error:
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.2.0:generate-sources (default-generate-sources) on project callerid: Execution default-generate-sources of goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.2.0:generate-sources failed: Invalid SDK: Platform/API level 15 not available. This command should give you all you need:
/home/jenkinsslave/data/tools/android-sdk/tools/android update sdk --no-ui --obsolete --force
Running that command fixes the problem. All I'm saying is that this problem should be automatically resolved when it does happen, or it shouldn't happen at all.
Thanks!
|
|
Project:
|
Jenkins
|
|
Priority:
|
Major
|
|
Reporter:
|
candrews
|
|
|
|
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
|
|
If you use the "Install Android project prerequisites" build step, any required Android platform images will be detected and installed automatically if not already available.
I'd rather not update the SDK itself automatically, as often the SDK Tools component introduces build-breaking Ant changes.
Is that sufficient?