The question seems very generic but I have a concrete (corner?) case in mind.
I have 3 flavors and I test them in Jenkins with some default settings which are good for us developers. However, when I want to release them, I want different preferences for the user, sometimes even more than one kind per flavor. For this, I created different buildTypes, let's say for example that I want Flavor1-ReleaseFlavor1 where I use a predefined set of preferences. In this case, the build type ReleaseFlavor1 is specific to Flavor1, and when generating the tasks, I would have many meaningless combinations like Flavor2-ReleaseFlavor1. Now, related to the topic question: - is it ok and I should just ignore those builds when running assemble? -> big waste of time waiting for the extra meaningless builds - should I avoid running assemble? -> I lose a quick way to build all the variants I might need - is there a way to filter out undesired combinations? -> this would make sense -- You received this message because you are subscribed to the Google Groups "adt-dev" 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.
