If I have a Multi-Configuration build ("myjob") with two axes (appFlavor: "Internal" or "External"; appVariant: "Prod" or "Debug") I get the following structure on S3:

jobs/appFlavor=Internal,appVariant=Prod,label=android/#/
jobs/appFlavor=External,appVariant=Prod,label=android/#/
jobs/appFlavor=Internal,appVariant=Debug,label=android/#/
jobs/appFlavor=External,appVariant=Debug,label=android/#/

I would like to see either:
jobs/myjob-appFlavor=Internal,appVariant=Prod,label=android/#/
jobs/myjob-appFlavor=External,appVariant=Prod,label=android/#/
jobs/myjob-appFlavor=Internal,appVariant=Debug,label=android/#/
jobs/myjob-appFlavor=External,appVariant=Debug,label=android/#/

or

jobs/myjob/appFlavor=Internal,appVariant=Prod,label=android/#/
jobs/myjob/appFlavor=External,appVariant=Prod,label=android/#/
jobs/myjob/appFlavor=Internal,appVariant=Debug,label=android/#/
jobs/myjob/appFlavor=External,appVariant=Debug,label=android/#/

I have two jobs with the same Axes/values, and I currently end up with collisions on S3 because the parent job name is not used in constructing the file key.