Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12821

android.device

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Activity

          @Christopher Orr I finally managed to find time to log the issue in the AOSP issue tracker.

          http://code.google.com/p/android/issues/detail?id=60024

          oldelvet Richard Mortimer added a comment - @Christopher Orr I finally managed to find time to log the issue in the AOSP issue tracker. http://code.google.com/p/android/issues/detail?id=60024

          For reference the fix to workaround the broken AOSP functionality is at
          https://github.com/jenkinsci/android-emulator-plugin/pull/27

          oldelvet Richard Mortimer added a comment - For reference the fix to workaround the broken AOSP functionality is at https://github.com/jenkinsci/android-emulator-plugin/pull/27

          Version 2.11 of the plugin has been released including these fixes

          orrc Christopher Orr added a comment - Version 2.11 of the plugin has been released including these fixes

          I just upgraded to 2.11(.1) specifically because I started having this issue recently and am now facing another weird one which seems related:

          After the plugin starts the emulator, its subsequent attempts to "connect" to it fail and ends up timing out. I see the emulator window available, but the sequence of "adb connect emulator-xxxx" and "adb -s emulator-xxxx shell getprop dev.bootcomplete" keeps on failing with a "error: device offline" error.

          any tips as to what could be the problem?

          randroid Roberto Andrade added a comment - I just upgraded to 2.11(.1) specifically because I started having this issue recently and am now facing another weird one which seems related: After the plugin starts the emulator, its subsequent attempts to "connect" to it fail and ends up timing out. I see the emulator window available, but the sequence of "adb connect emulator-xxxx" and "adb -s emulator-xxxx shell getprop dev.bootcomplete" keeps on failing with a "error: device offline" error. any tips as to what could be the problem?

          I reopened https://issues.jenkins-ci.org/browse/JENKINS-11952 as it seems to be a better fit for the issue description, but I think it might have been caused by the changes that fixed this issue.

          randroid Roberto Andrade added a comment - I reopened https://issues.jenkins-ci.org/browse/JENKINS-11952 as it seems to be a better fit for the issue description, but I think it might have been caused by the changes that fixed this issue.

          People

            oldelvet Richard Mortimer
            sebl29 Sebastian Schefczyk
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: