Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N notebook
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mark Stevens
  • notebook
  • Wiki
  • build server instrumented testing

Last edited by Mark Stevens Mar 30, 2017
Page history

build server instrumented testing

Below Items discuss ways to setup ADB for remote adb access to use for instrumented testing

Setup a mac/win/linux machine (adb controller) to connect to 7 devices over adb (or 14 with two root usb hubs)

  1. adb version on abd-controller must match version on build server image
  2. run adb in listen all mode on adb controller adb -a -P 5037 fork-server server&
  3. setup alias on build server alias adb='adb -H <hostname>' where hostname is ip/hostname of adb-controller
  4. gradlew connected

I had a similar situation. I work on a remote desktop for development but my android device is connected to my local laptop. I wanted to be able to use adb and the android plugin in eclipse on the remote desktop and connect to the device attached to my laptop. After searching on the internet and not finding anything that really helped, I decided to write a port forwarder that would do the trick. You can find it here. I hope it will be helpful to other people as well.


Beginning Android 4.3 you can:

  1. Make adb server listen on all interfaces. You have two options:
  • Make gListen=1 and recompile adb (I have compiled it on Linux-x64 machine for you and put it here)
  • Start adb server with -a parameter: adb -a -P 5037 fork-server server&
  1. Use adb on your remote machine with extra parameter, e.g. adb -H <remote_host> shell
Clone repository
  • branch code plan
  • build and test configuration
  • build artifact versioning
  • build server instrumented testing
  • build server move
  • bzt16wifi02 releases
  • bzt18uxa02 releases
  • configuration settings and permissions
  • create a repo from cli in gitlab
  • engineering status
  • feature deployment
  • gitlab installation instructions
  • Home
  • ota update and deployment
  • qbert implementation
View All Pages