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

Jenkins stops job when restart test app

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: ant-plugin
    • Labels:
    • Environment:
      Jenkins 2.19.4
      macOS 10.12.1
      Android 4.4.4, 5.0, 5.1, 6.0
      Ant 1.9.7
    • Similar Issues:

      Description

      I'm working with Jenkins, Appium and Ant. When I start the the test by Ant via Terminal, everything run smooth. But, when I start the test by invoking Ant via Jenkins, I notice that Jenkins force-stop the app instead of restart it (tested on real Android devices and Genymotion).

      I found that something weird in the logs at the moment the app restarts, the test app is launched but it is killed by Jenkins, the Appium server responds DETELE instead of GET if I start the test via Jenkins:

      Terminal:

      [debug] [ADB] 1 device(s) connected
      [debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform- tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","am","start","-n","com.xxx/im.actor.XXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x10200000"]
      [Appium] New AndroidDriver session created successfully, session d813f8ab-37c1-4f66-8b70-3008eb833c77 added to master session list
      [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...
      [HTTP] <-- POST /wd/hub/session 200 3205 ms - 881 
      [HTTP] --> POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts {"type":"implicit","ms":10000}
      [MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",10000,"d813f8ab...
      [debug] [BaseDriver] Set implicit wait to 10000ms
      [MJSONWP] Responding to client with driver.timeouts() result: null
      [HTTP] <-- POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts 200 3 ms - 76 
      [HTTP] --> GET /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/appium/device/current_activity {}
      [MJSONWP] Calling AppiumDriver.getCurrentActivity() with args: ["d813f8ab-37c1-4f66-8b70-3...
      [debug] [ADB] Getting focused package and activity
      [debug] [ADB] Getting connected devices...
      [debug] [ADB] 1 device(s) connected
      [debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","dumpsys","window","windows"]
      [MJSONWP] Responding to client with driver.getCurrentActivity() result: "im.actor.SplashActivity"
      

      Jenkins:

      [testng] [debug] [ADB] 1 device(s) connected
      [testng] [debug] [ADB] Running /Users/xxxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","am","start","-n","com.xxx/im.actor.XXXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x10200000"]
      [testng] [Appium] New AndroidDriver session created successfully, session 464902e9-5406-4d1e-915e-d4fad4e39da8 added to master session list
      [testng] [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...
      [testng] [HTTP] <-- POST /wd/hub/session 200 3865 ms - 881 
      [testng] [HTTP] --> POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts {"type":"implicit","ms":20000}
      [testng] [MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",20000,"464902e9...
      [testng] [debug] [BaseDriver] Set implicit wait to 20000ms
      [testng] [MJSONWP] Responding to client with driver.timeouts() result: null
      [testng] [HTTP] <-- POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts 200 4 ms - 76 
      [testng] [HTTP] --> DELETE /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8 {}
      [testng] [MJSONWP] Calling AppiumDriver.deleteSession() with args: ["464902e9-5406-4d1e-915e-d...
      [testng] [debug] [AndroidDriver] Shutting down Android driver
      [testng] [debug] [ADB] Getting connected devices...
      [testng] [debug] [ADB] 1 device(s) connected
      [testng] [debug] [ADB] Running /Users/xxxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","am","force-stop","com.xxx"]
      

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Reassigned to the Ant Plugin maintainer. BTW, please provide the job configuration and Ant definition at least

          Show
          oleg_nenashev Oleg Nenashev added a comment - Reassigned to the Ant Plugin maintainer. BTW, please provide the job configuration and Ant definition at least
          Hide
          chip Chip Li added a comment -

          how can I export job config and ant definition?

          Show
          chip Chip Li added a comment - how can I export job config and ant definition?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Job config: Jenkins CLI's get-job: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI
          Ant definition: No idea, depends on your job configuration Likely you store it somewhere in SCM

          Show
          oleg_nenashev Oleg Nenashev added a comment - Job config: Jenkins CLI's get-job: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI Ant definition: No idea, depends on your job configuration Likely you store it somewhere in SCM
          Hide
          chip Chip Li added a comment -

          I've no idea how to use Jenkins CLI to get job. But I attached my job config.xml

          Show
          chip Chip Li added a comment - I've no idea how to use Jenkins CLI to get job. But I attached my job config.xml
          Hide
          oleg_nenashev Oleg Nenashev added a comment - - edited

          OK, it invokes Ant.
          Then you need to follow-up on the ticket with plugin maintainers.

          P.S: Unfollowing the ticket since it's not my area

          Show
          oleg_nenashev Oleg Nenashev added a comment - - edited OK, it invokes Ant. Then you need to follow-up on the ticket with plugin maintainers. P.S: Unfollowing the ticket since it's not my area
          Hide
          chip Chip Li added a comment -

          ok thanks.

          Show
          chip Chip Li added a comment - ok thanks.
          Hide
          chip Chip Li added a comment -

          I resolved this issue. Using restart app function by Appium instead of adb command.

          Show
          chip Chip Li added a comment - I resolved this issue. Using restart app function by Appium instead of adb command.

            People

            • Assignee:
              chip Chip Li
              Reporter:
              chip Chip Li
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: