I am build an automated uploader for Unity Cloud Build that will upload our assetbundles to our content delivery. We would like to structure things automatically with our version numbers being the same for every build (and if we have a new platform the next version would simple just add that platform’s subfolder into our system). This only works (in an automated way) if the UCB is consistent between all platforms.
The reason is that it’d be easier to communicate in the studio if issues could be tracked by platform independent version number as well as it’d play nicer with our other systems.
No we don’t support multiple platforms for a single target. The consistent numbering of builds across targets however is something we have heard requested several times before and are still discussing if this is something that could be made available (and how that would even work).
You could just start relying on the commit id to refer to specific builds rather than relying on the build number generated by Cloud Build. The commit id is provided in the Build Manifest which you could even display in game somewhere.
Alright, thanks. The problem with using the commit id is that we might have separate branches running for android and ios during certain stages of our development, which fractures the commit id consistency. There are multiple different work-arounds that we could do, but most are either overkill or a manual system. For now, we’ll just rely on the manually set PlayerSettings.bundleVersion.
Even if instead of having multiple platforms, just being able to group multiple UCB targets into one button and that button having a master build number and a dictionary of subTarget:build#.