I am trying to generate baseline profiles for the app. As it seems this would be good to have those generated on every release build as code changes constantly and the reason for a new build is of course code change so baseline would need an update. Problem I see with that is that code that the baseline is ran on should be the closest to production one, meaning f.e. not mocking data on network layer i.e. calling backend services for data using Retrofit etc.. This means a test running on a CI and a network failure, test instability, change in data responses so test fails to match some results will result in a build failure. This seems to be a high risk thing from maintenance purpose. Is there any smart way to tackle this? Or maybe I am overthinking this and the baseline profile generation attached to CI release build process is over engineering? Maybe a baseline profile generated locally now and then and updated like every 2 weeks is enough? What do you think?