Hi Folks, Good day to you We recently configured the configuration cache on our bitrise CI and have noticed that it doesn’t work most of the time. We have observed logs like this in our build logs:

Calculating task graph as the configuration cache cannot be reused because the environment variable '<Some env variable name>' has changed.

Upon investigation, we discovered that the root cause of this issue is the environment variables that are not exposed to the PRs. Our current setup for the configuration cache involves creating it on non-PR builds via a workflow. This workflow triggers when any PR gets merged into develop, saving the cache. Subsequently, any new PR can utilize the configuration cache. Do you have any recommendations on how we can resolve this issue? Is there any way we can ignore some variables for cache to so it doesn’t get invalidated. TIA!

I don't know of a way to suppress cache invalidation for env vars. I'd focus on changing your build logic to not rely on that variable anymore, making your configuration cache actually stable between non-PR and PR builds