[JIRA] [android-emulator] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails
David Müller commented on JENKINS-13785 Use Google Apis SDK Add-on via Target ID fails Sorry for the delay in responding - with actual Versions of the jenkins android emulator plugin it now works. I'm not sure what else I changed, I might have simply forgotten to put the target in quotes, like Google Inc.:Google APIs:7 instead of "Google Inc.:Google APIs:7". That part of the jenkins job history is lost, so I can't be sure. The build problems I meant where: the sdk could not be downloaded, or the integration tests failed to run on the emulator like this: ERROR Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.1.1:internal-integration-test (default-internal-integration-test) I remember this happened always when I configured the android emulator plugin for "Run emulator with properties". I worked around the problem by manually updateing the sdks, and starting the matrix build once with "Run emulator with properties", thereby creating the avds, and then changing the configuration to "Run existing emulator". As stated above, this is not neccessary anymore with the actual versions of maven android and Jenkins android Emulator plugins. Thanks a lot for the plugin! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14857) Android Lint Plugin does nothing
David Müller reopened JENKINS-14857 Android Lint Plugin does nothing Please provide a fix for this, this plugin is too useful to keep away from maven users. A suitable maven phase would be the "verify" (See Maven Livecyles). If a goal is really needed, I would suggest "android:emma" Available goals from the android maven plugin are listed here: http://maven-android-plugin-m2site.googlecode.com/svn/plugin-info.html I would be glad to test new plugin versions. Change By: David Müller (09/Dec/12 1:47 AM) Resolution: WontFix Status: Resolved Reopened 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
[JIRA] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails
David Müller created JENKINS-13785:
--
Summary: 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.
--
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
[JIRA] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails
[
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
