search

bitrise-steplib / steps-gradle-runner

MIT License
10 stars 28 forks source link

Is there any way to provide specific folder pattern to search for APK and AAB? #67

Closed amatkivskiy closed 3 years ago

amatkivskiy commented 5 years ago

Hi all,

Recently our team has switched to Google Play deployment using Android Bundles. For that to implement throw CI flow we needed to export *.aab files. We figured out that during build process gradle produces multiple .aab files (not only in output directory but also intermediate bundles in /build/intermediates/intermediary_bundle/_build_variant_name/). This causes step to deploy wrong .aab file.

So seems it will be nice to specify folder path under which step should find proper artifacts like /build/outputs/*.aab. Is this possible?

Roland-Bak commented 5 years ago

Hi there @amatkivskiy 👋

You can filter the .aab files moved to the deploy folder by updating the APK and AAB file include filter in the Export Configs section 🙂

amatkivskiy commented 5 years ago

@Roland-Bak ok, can I specify not all *.aab file but only *.aab files under specific directory? Like : ./app/build/outputs/bundle/**.aab

bitce commented 5 years ago

Hi @amatkivskiy! That is also an option, but alternatively, you can specify the wanted type of .aab-s in the include filter

amatkivskiy commented 5 years ago

@bitce Can you please specify an example ?

guness commented 5 years ago

I am also experiencing same issue. both file names are same, they are just in different directories. so I have fixed it by specifying an exclude filter like */intermediates/*.aab

github-actions[bot] commented 3 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

github-actions[bot] commented 3 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.