[JIRA] (JENKINS-12821) android.device

Sebastian Schefczyk created JENKINS-12821:
---------------------------------------------

             Summary: android.device
                 Key: JENKINS-12821
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
             Project: Jenkins
          Issue Type: Bug
          Components: android-emulator
    Affects Versions: current
            Reporter: Sebastian Schefczyk
            Assignee: Christopher Orr
            Priority: Minor


The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
Commenting this line will find the emulator.
On my local machine this is working fine, but not in Jenkins.
Both machines use maven 3.0.4 on Linux/Ubuntu.

<groupId>com.jayway.maven.plugins.android.generation2</groupId>
<artifactId>android-maven-plugin</artifactId>
<configuration>
   ...
  <device>emulator</device>
   ...
</configuration>
</plugin>

This configuration is useful on the local machine, if you are developing while charging your phone via USB.
Best regards, that's a really nice plugin!
 Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159213#comment-159213 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

I suspect this may be due to the android-emulator-plugin starting a new ADB instance for each running job. This means that the android-maven-plugin may not find the ADB instance that contains the emulator.

I have had a niggling suspicion that this may be the case for a while because I have seen matrix based testing fail at times and I suspect this happens when two emulators/ADB are running on the same slave at once.

It may be that android-maven-plugin never finds a second ADB instance running on a non-standard port and hence if there is any other (non-Jenkins related) ADB hanging around things will fail.

You may find that adding
{code}
-Dandroid.device=${ANDROID_AVD_DEVICE}
{code}
to the jobs maven goals and options configuration will fix it (this specifies the exact emulator device to use). However I suspect that may fail if my hypothesis about my matrix build failures is correct.

               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Christopher Orr
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159215#comment-159215 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

Looking at recent ddmlib.jar (the library that android-maven-plugin uses to talk to ABD) source code it looks like the only way to change the ADB port number is by setting environment variable
{{ANDROID_ADB_SERVER_PORT}} to the required port number before invoking maven. As per source code at com.android.ddmlib.AndroidDebugBridge#determineAndValidateAdbPort() from sdk/ddms/libs/ddmlib in the Android Git repos.
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Christopher Orr
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159219#comment-159219 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

Please disregard my previous two comments. The plugin does seem to already ANDROID_ADB_SERVER_PORT so that should just magically work.
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Christopher Orr
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159285#comment-159285 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

So I decided to investigate this a bit more and took the radical step of setting -Dandroid.device=emulator in my Jenkins maven commandline. The good(!) news is I get the same error here plus I've got a build environment setup for android-maven-plugin so I should be able to dig a little deeper over the next couple of days.

For the record I get the following stack trace with plugin a-m-p 3.1.1 (get similar with 3.0.0 too).

{code}
[INFO] Waiting for initial device list from the Android Debug Bridge
[INFO] Found 1 devices connected with the Android Debug Bridge
[INFO] android.device parameter set to emulator

...snip...

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:01.522s
[INFO] Finished at: Mon Feb 20 15:20:59 GMT 2012
[INFO] Final Memory: 15M/495M
[INFO] ------------------------------------------------------------------------
mavenExecutionResult exceptions not empty
message : Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.1.1:internal-pre-integration-test (default-internal-pre-integration-test) on project mobilemax-it: No device found for android.device=emulator
cause : No device found for android.device=emulator
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.1.1:internal-pre-integration-test (default-internal-pre-integration-test) on project mobilemax-it: No device found for android.device=emulator
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
        at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
        at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
        at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
        at hudson.remoting.UserRequest.perform(UserRequest.java:118)
        at hudson.remoting.UserRequest.perform(UserRequest.java:48)
        at hudson.remoting.Request$2.run(Request.java:287)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.maven.plugin.MojoExecutionException: No device found for android.device=emulator
        at com.jayway.maven.plugins.android.AbstractAndroidMojo.doWithDevices(AbstractAndroidMojo.java:602)
        at com.jayway.maven.plugins.android.AbstractAndroidMojo.undeployApk(AbstractAndroidMojo.java:644)
        at com.jayway.maven.plugins.android.AbstractAndroidMojo.undeployApk(AbstractAndroidMojo.java:628)
        at com.jayway.maven.plugins.android.AbstractAndroidMojo.deployDependencies(AbstractAndroidMojo.java:538)
        at com.jayway.maven.plugins.android.phase11preintegrationtest.InternalPreIntegrationTestMojo.execute(InternalPreIntegrationTestMojo.java:36)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        ... 27 more
{code}

               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Christopher Orr
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mortimer reassigned JENKINS-12821:
------------------------------------------

    Assignee: Richard Mortimer  (was: Christopher Orr)
   

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Richard Mortimer
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159333#comment-159333 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

After adding some instrumentation to android-maven-plugin it seems that ddmlib.jar (the Android library that interfaces with the emulator/device) is not reporting the emulator as being an emulator.

{code}
[INFO] Waiting for initial device list from the Android Debug Bridge
[INFO] Found 1 devices connected with the Android Debug Bridge
[INFO] android.device parameter set to emulator
[INFO] checking device=localhost_47048_unknown_sdk, port=58222, name=null, isEmulator=false
{code}

Looking at the ddmlib.jar source code the isEmulator method detects an emulator based on the serial number of the device. In particular it expects it to confirm to the following regexp pattern.

{code}
    /** Emulator Serial Number regexp. */
    final static String RE_EMULATOR_SN = "emulator-(\\d+)"; //$NON-NLS-1$

{code}

android-emulator-plugin seems to use a different serial number format to manually launched emulator instances. Manual launched serial numbers resemble {{emulator-5554}} whereas the android emulator version is {{localhost:5554}}.

So far I have not identified where the serial number is generated/set but it does look like this issue comes down to the serial number format.
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Richard Mortimer
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159349#comment-159349 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

Problem found. Unfortunately it is deep in the emulator (qemu) startup code. The following code registers the emulator instance with the adb server.

{code}
qemu-setup.c:
  sprintf(tmp,"0012host:emulator:%d",base_port+1);
  socket_send(s, tmp, 18+4);
{code}

This registers the emulator with the adb server but it makes two assumptions:
# that the user port is one less than the adb port for the emulator. Comments in the code also suggest that the user port was once assumed to be an even number. The server takes the adb port number supplied and subtracts one to get the user port. It then tries to connect to the user port to confirm that it really is an emulator.
# only 4 characters of the adb port number is sent to the adb server (the +4 in socket_send). Thus if the port number is greater than 9999 or less than 1000 then the wrong port number is sent.

I haven't searched the Android bug database for this yet but will search/report there later today.

However that does not make things work for a-e-p because we will need to support older emulators.

I tested a fix that uses the Jenkins port allocator to allocate 7000 for user port, 7001 for emulator adb port and then 8000 for the adb server. With that maven happily worked using {{-Dandroid.device=emulator}}.

{code}
[INFO] Found 1 devices connected with the Android Debug Bridge
[INFO] android.device parameter set to emulator
[INFO] checking device=emulator-6000_hudson_en-GB_160_WVGA_android-7_unknown_sdk, port=8000, name=hudson_en-GB_160_WVGA_android-7, isEmulator=true
[INFO] Emulator emulator-6000_hudson_en-GB_160_WVGA_android-7_unknown_sdk found.
{code}

Obviously to provide a proper fix we need to do some magic with the port allocator plugin. Assuming that it is acceptable that we require a newer port allocator plugin for a-e-p then I'll look to extend that to help us. Failing that we can likely make the existing allocator work with a bit of messing around.
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Richard Mortimer
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159389#comment-159389 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

Proof of concept fix committed to my personal github a-e-p fork.
https://github.com/oldelvet/android-emulator-plugin/tree/jenkins-12821-poc

I intend to implement the port allocator side of this in due course but have verified that the fix allows android.device=emulator to work with the proof of concept.
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Richard Mortimer
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160695#comment-160695 ]

Christopher Orr commented on JENKINS-12821:
-------------------------------------------

Great stuff.

Did you file that Android bug, out of interest?
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Richard Mortimer
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160950#comment-160950 ]

Richard Mortimer commented on JENKINS-12821:
--------------------------------------------

No I didn't get around to filing it. With the new SDK being out I figure I ought to test against that before reporting it now.
               

> android.device
> ---------------
>
>                 Key: JENKINS-12821
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821
>             Project: Jenkins
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>            Reporter: Sebastian Schefczyk
>            Assignee: Richard Mortimer
>            Priority: Minor
>
> The following configuration of the android-maven-plugin will not find the running emulator on Jenkins.
> Commenting this line will find the emulator.
> On my local machine this is working fine, but not in Jenkins.
> Both machines use maven 3.0.4 on Linux/Ubuntu.
> <groupId>com.jayway.maven.plugins.android.generation2</groupId>
> <artifactId>android-maven-plugin</artifactId>
> <configuration>
>    ...
>   <device>emulator</device>
>    ...
> </configuration>
> </plugin>
> This configuration is useful on the local machine, if you are developing while charging your phone via USB.
> Best regards, that's a really nice plugin!
>  Sebl29

--
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