#18830 Sharing mypy cache for the same project with different buildroots Issue created by csqzhang Is your feature request related to a problem? Please describe. I'd would like to report an issue when we migrate to pants 2.15 from 2.14. We use Pants in our Jenkins CI/CD pipeline. In our setup, Jenkins will work on each pipeline in different folders. For example, a branch name AB would be under

/tmp/workspace/AB

, and branch name CD would be under

/tmp/workspace/CD

. We notice that Pants will not be able to share mypy cache across branch after 2.15. I believe the issue comes from this pull request #18061. It seems that Pants now replies on buildroot (e.g. a path) to differentiate repos. ref: https://pantsbuild.slack.com/archives/C046T6T9U/p1682039225688279 Describe the solution you'd like 1. Provide an option to disable the option of creating mypy cache per buildroot? or 2. use some pre-defined env variable to decide the repo? Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here. pantsbuild/pants