PHPStan caching strategy per branch

[mkeromen]

Hi,

I'm using Gitlab to deploy my codebase.
Each time, I deploy a branch (in fact multiple times by day), my CI do the following things (very simplified) :

1. Create a specific deploy folder with my branch name and clone whole project inside

# branch-1
/data/www/branch-1/....
# branch-2
/data/www/branch-2/....

2. Run PHPStan (with no overriden configuration)

- cd /data/www/branch-1
- bin/phpstan analyze --level 1 --no-progress

So, by default my caching folder is set to /tmp/phpstan. This folder is getting bigger and bigger.
For now, I have a cron that delete the folder periodically but it seems like a workaround...

Can I use a better approach in my CI/CD to maintain a reasonnable /tmp/phpstan folder size and not broke the performance of caching ?

[ondrejmirtes]

The problem is that you're analysing your files with different paths so the cache gets bigger over time as PHPStan doesn't recognize these are the same files.

As the cache is cold in these cases anyway, I recommend you to use different tmpDir per deploy.

[mkeromen]

Thanks for your answer. Just to clarify your point. Maybe I could have :

• A tmp dir to store my cache per branch (because I can have multiple build for one feature) /data/www/branch-1/tmpDir
  So first time, cache is cold but subsequents deployments can use it.
• When my branch is merged, I destroy it (and my phpstan cache too)