From @motorro on Thu Oct 13 2016 08:12:07 GMT-0400 (EDT)
As an android programmer I’m eager to get support for multiple apk builds in Android workflow.
Say I have a multi-variant application or a platform apk split and want them signed and deployed. Let’s take the latter case for example.
When build is performed I have a set of apk (one per platform):
app-x86-release-unsigned.apk app-x86_64-release-unsigned.apk ... app-armeabi-release-unsigned.apk
The problem is only the single file is put to variable
$BITRISE_APK_PATH (log abstract):
Move apk files... find "." "-name" "*.apk" "!" "-name" "*-unaligned.apk" copy ./app/build/outputs/apk/app-x86-release-unsigned.apk to /bitrise/deploy/app-x86-release-unsigned.apk copy ./app/build/outputs/apk/app-mips-release-unsigned.apk to /bitrise/deploy/app-mips-release-unsigned.apk copy ./app/build/outputs/apk/app-x86_64-release-unsigned.apk to /bitrise/deploy/app-x86_64-release-unsigned.apk copy ./app/build/outputs/apk/app-mips64-release-unsigned.apk to /bitrise/deploy/app-mips64-release-unsigned.apk copy ./app/build/outputs/apk/app-arm64-v8a-release.apk to /bitrise/deploy/app-arm64-v8a-release-unsigned.apk copy ./app/build/outputs/apk/app-armeabi-v7a-release-unsigned.apk to /bitrise/deploy/app-armeabi-v7a-release-unsigned.apk copy ./app/build/outputs/apk/app-armeabi-release-unsigned.apk to /bitrise/deploy/app-armeabi-release-unsigned.apk The apk path is now available in the Environment Variable: $BITRISE_APK_PATH (value: /bitrise/deploy/app-armeabi-release-unsignedapk)
The signing step also uses the single file as an input.
It will be great if some export var from build step could contain just an output directory and signing (and may be other steps) use this dir to iterate apk-files rather than use a single one.
Copied from original issue: https://github.com/bitrise-io/bitrise.io/issues/76