[TASK] Do not cache phpstan in CI

phpstan almost always triggers a full recalculation ignoring
cache in CI. We switch phpstan CI cache config to /tmp which
is not cached by CI to save some memory.

Resolves: #98014
Releases: main, 11.5
Change-Id: I0bf2c72f529e9f179eb4becaac4d164cad8c318a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75276


Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

Build/gitlab-ci/nightly/integrity.yml

@@ -95,23 +95,6 @@ phpstan php 7.4:
   needs: []
   only:
     - schedules
-  cache:
-    key: 11.5-composer-phpstan-74
-    paths:
-      - .cache
   script:
     - Build/Scripts/runTests.sh -s composerInstall -p 7.4
     - Build/Scripts/runTests.sh -s phpstan -p 7.4
-
-phpstan php 8.1:
-  stage: integrity
-  needs: []
-  only:
-    - schedules
-  cache:
-    key: 11.5-composer-phpstan-81
-    paths:
-      - .cache
-  script:
-    - Build/Scripts/runTests.sh -s composerInstall -p 8.1
-    - Build/Scripts/runTests.sh -s phpstan -p 8.1

Build/gitlab-ci/pre-merge/integrity.yml

@@ -79,25 +79,6 @@ phpstan php 7.4 pre-merge:
     refs:
       - schedules
       - "11.5"
-  cache:
-    key: 11.5-composer-phpstan-74
-    paths:
-      - .cache
   script:
     - Build/Scripts/runTests.sh -s composerInstall -p 7.4
     - Build/Scripts/runTests.sh -s phpstan -p 7.4
-
-phpstan php 8.1 pre-merge:
-  stage: main
-  except:
-    refs:
-      - schedules
-      - "11.5"
-  cache:
-    key: 11.5-composer-phpstan-81
-    paths:
-      - .cache
-  script:
-    - Build/Scripts/runTests.sh -s composerInstall -p 8.1
-    - Build/Scripts/runTests.sh -s phpstan -p 8.1
-

Build/phpstan/phpstan.ci.neon

@@ -2,6 +2,10 @@ includes:
   - phpstan.neon
 
 parameters:
+  # CI needs to calculate phpstan a-new each time anyways. No point in caching this.
+  # We write this to /tmp within container which is not cached by CI.
+  tmpDir: /tmp
+
   parallel:
     # Don't be overly greedy on machines with more CPU's to be a good neighbor especially on CI
     maximumNumberOfProcesses: 5