Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 558956]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Gradle Managed Devices couples itself to the codebase it's configured for and creates dependencies on the app & tests in it. This is great if you want a quick bootstrap to run a build AND test it all at once.
In order to maximize a CI pipeline, it is often preferable parallelize jobs (building, testing UI, unit testing, integration testing, linting, etc).
In this scenario, it may be optimal to build APKs (target & test APKs) and to use those built APKs from one job in another and run those on a machine designed for virtualization and/or optimized for running emulators/UI tests/specific connected hardware devices, where shipping all of the compiled code, dependencies, etc to the UI testing machine would be slow (due to # of files, size of files, etc).
Ideally, GMD would enable us to run a test APK against an app APK and run that on the GMD devices without strictly needing to compile the codebase again.