[
https://issues.jenkins-ci.org/browse/JENKINS-13785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Müller updated JENKINS-13785:
-----------------------------------
Description:
I want to run a Matrix Job with Google Apis for instrumentation tests
Simply using the name from the "android list target" command like "Google
Inc.:Google APIs:7" leads to problems in the build because of the spaces in the
name.
When trying to use the target id it gives me mixed results, the plugin seems
not to recognize the id.
For example, from the Konsole output:
First, using id 27, which stands for "Google Inc.:Google APIs:15" in my
environment
{noformat}
$ /opt/android-sdk-linux/tools/android list target
[android] The configured Android platform needs to be installed: 27
[android] Installing the '27' SDK component(s)...
$ /opt/android-sdk-linux/tools/android update sdk -o -u -t 27
Error: Flag '-o' is not valid for 'update sdk'.
[...]
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_27.avd
[android] Setting hardware properties:
{noformat}
This build ultimately succeeds, although no sdk can be installed.
Second, using id 6, which stands for "Google Inc.:Google APIs:7" in my
environment
{noformat}
[android] The configured Android platform needs to be installed: android-6
[android] Installing the 'android-6' SDK component(s)...
Error: Flag '-o' is not valid for 'update sdk'.
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_android-6.avd
[android] Failed to run AVD creation command
Error: Target id is not valid. Use 'android list targets' to get the
target ids.
{noformat}
This build fails, because no Android 6 is not available locally.
Now, the use of ids would only be a workaround, as the ids are dependent on the
sdk installation.
But failing a way to replace the whitespaces in the name, it would be nice if
the plugin would use the ids in the correct way when calling the android cli
tools.
When parsing the output from list targets, the plugin should recognize target
ids.
was:
I want to run a Matrix Job with Google Apis for instrumentation tests
Simply using the name from the "android list target" command like "Google
Inc.:Google APIs:7" leads to problems in the build because of the spaces in the
name.
When trying to use the target id it gives me mixed results, the plugin seems
not to recognize the id.
For example, from the Konsole output:
First, using id 27, which stands for "Google Inc.:Google APIs:15" in my
environment
{noformat}
$ /opt/android-sdk-linux/tools/android list target
[android] The configured Android platform needs to be installed: 27
[android] Installing the '27' SDK component(s)...
$ /opt/android-sdk-linux/tools/android update sdk -o -u -t 27
Error: Flag '-o' is not valid for 'update sdk'.
[...]
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_27.avd
[android] Setting hardware properties:
{noformat}
This build ultimately succeeds, although no sdk can be installed.
Second, using id 6, which stands for "Google Inc.:Google APIs:7" in my
environment
{noformat}
[android] The configured Android platform needs to be installed: android-6
[android] Installing the 'android-6' SDK component(s)...
Error: Flag '-o' is not valid for 'update sdk'.
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_android-6.avd
[android] Failed to run AVD creation command
Error: Target id is not valid. Use 'android list targets' to get the
target ids.
{noformat}
This build fails, because no Android 6 is not available locally.
Now, the use of ids would only be a workaround, as the ids are dependent on the
sdk installation.
But failing a way to replace the whitespaces in the name, it would be nice if
the plugin would use the ids in the correct way when calling the android cli
tools.
> Use Google Apis SDK Add-on via Target ID fails
> ----------------------------------------------
>
> Key: JENKINS-13785
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13785
> Project: Jenkins
> Issue Type: Bug
> Components: android-emulator
> Affects Versions: current
> Environment: Ubuntu Server x64, Running Jenkins stand-alone, Matrix
> build, using maven.
> Reporter: David Müller
> Assignee: Christopher Orr
>
> I want to run a Matrix Job with Google Apis for instrumentation tests
> Simply using the name from the "android list target" command like "Google
> Inc.:Google APIs:7" leads to problems in the build because of the spaces in
> the name.
> When trying to use the target id it gives me mixed results, the plugin seems
> not to recognize the id.
> For example, from the Konsole output:
> First, using id 27, which stands for "Google Inc.:Google APIs:15" in my
> environment
> {noformat}
> $ /opt/android-sdk-linux/tools/android list target
> [android] The configured Android platform needs to be installed: 27
> [android] Installing the '27' SDK component(s)...
> $ /opt/android-sdk-linux/tools/android update sdk -o -u -t 27
> Error: Flag '-o' is not valid for 'update sdk'.
> [...]
> [android] Using Android SDK: /opt/android-sdk-linux
> [android] Creating Android AVD:
> /var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_27.avd
> [android] Setting hardware properties:
> {noformat}
> This build ultimately succeeds, although no sdk can be installed.
> Second, using id 6, which stands for "Google Inc.:Google APIs:7" in my
> environment
> {noformat}
> [android] The configured Android platform needs to be installed: android-6
> [android] Installing the 'android-6' SDK component(s)...
> Error: Flag '-o' is not valid for 'update sdk'.
> [android] Creating Android AVD:
> /var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_android-6.avd
> [android] Failed to run AVD creation command
> Error: Target id is not valid. Use 'android list targets' to get the
> target ids.
> {noformat}
> This build fails, because no Android 6 is not available locally.
> Now, the use of ids would only be a workaround, as the ids are dependent on
> the sdk installation.
> But failing a way to replace the whitespaces in the name, it would be nice if
> the plugin would use the ids in the correct way when calling the android cli
> tools.
> When parsing the output from list targets, the plugin should recognize target
> ids.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
