addressable_content_state.bin in practice?

Hello,

Currently, we have the addressable_content_state.bin which corresponds to the pair {BuildMachine, TargetPlatform}. I.e. it produces different results even for the same platform if built on different machines. There are 2 problems:

  1. this shouldn’t happen (it should only depend on the target platform);
  2. we need a different addressable_content_state.bin for different platforms to prevent us from managing separate branches. or, even better, a better system of tracking what was built. Also, note that we can also have dev/prod etc environments and those already require us to write some custom systems to not affect the ‘official’ addressable_content_state.bin when developing.

What is your way of managing a similar scenario, fellow developers?

help? :smile: