|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I'd say that it's really unlikely that this would get implemented any time soon.
Most people use two jobs and the usual Jenkins downstream build pattern for this purpose.
i.e. The first job builds the APK(s) and can fail fast if something goes wrong. If successful, it starts a downstream build of the second job, which starts an emulator, pulls the APK(s) from the first build and runs the tests etc.
This is also very useful for matrix jobs, where you want to test on multiple Android platforms, languages, screen densities etc., as you only need to build the APK once in a freestyle job, then kick off a downstream matrix job which runs the various different emulators.