84280[WIP][TASK] Include Git revision in package cache identifier
Commit message
Review
-
Code review CR 0
-
Verified V 0
Issues 1
Files 2
Review log 810
-
Andreas Kienast uploaded patch set 1 05/15/24, 08:25
-
Andreas Kienast uploaded patch set 2 05/15/24, 08:43
-
Andreas Kienast uploaded patch set 3 05/23/24, 06:43
-
Andreas Kienast wrote 05/23/24, 06:44
Unset private -
core-ci voted on patch set 3 V +1 05/23/24, 06:48 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/58095
-
Andreas Kienast uploaded patch set 4
V +105/23/24, 07:13 -
core-ci voted on patch set 4 V +1 05/23/24, 07:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/58096
-
Christian Kuhn commented on patch set 4 CR -1 05/23/24, 07:25
mmmh. this is for monorepo development only, right? since that git command is run in monorepo-clone-root because somehow that's the base directory of web requests? isn't this a bit of an overkill? shouldn't we require from core-devs to actually flush cashes when either working in such a related area that affects caches, and after pulling in new changes? also, when this is merged and kicks in, it will lead to the situation that multiple cache files accumulate over time and make the system even harder to understand when lots of old cache files (especially for central stuff like core system cache) are lying around ... apart from that ... running a git command via exec() to then include this as cache hash really does not feel good and i'd love to avoid this in general.Environment.php:337Unresolvedin which directory is this git command executed? -
Patrick Schriner commented on patch set 4 05/23/24, 09:26
Unresolved
Super cool idea, Can we extend it with an event? I'd love to be able the container hash in a clustered / docker / kubernetes environment to the cache identifier. -
Andreas Kienast abandoned the change 06/20/24, 10:23