fix: make vaadinBuildFrontend build cache relocatable (#25033) (CP: 25.2) - #25035
Conversation
The task cache key embedded absolute project paths, so a shared build cache never hit across checkouts at different locations. Directory inputs no longer contribute their absolute path to the key. Fixes #25030
|
This PR is eligible for auto-merging policy, so it has been approved automatically. If there are pending conditions, auto merge (with 'squash' method) has been enabled for this PR [Message is sent from bot] |
…table On 25.2 the default index.html is generated into the frontend root, and vaadinBuildFrontend declares it as an optional output. When the relocated copy carries that file, it has no task history in the fresh checkout, so Gradle treats it as an overlapping output and disables caching - the task safely rebuilds instead of loading from cache, so the FROM_CACHE assertion never held. Omit the generated frontend-root index.html from the relocated copy so the test exercises only the cache-key fix (no absolute project path in the key). Its content is not part of the key, so omitting it is safe and it is restored on the FROM_CACHE hit.
|
This PR is eligible for auto-merging policy, so it has been approved automatically. If there are pending conditions, auto merge (with 'squash' method) has been enabled for this PR[Message is sent from bot] |
|
This PR is eligible for auto-merging policy, so it has been approved automatically. If there are pending conditions, auto merge (with 'squash' method) has been enabled for this PR [Message is sent from bot] |
|
|
This ticket/PR has been released with Vaadin 25.2.4. |
3 participants
This PR cherry-picks changes from the original PR #25033 to branch 25.2.
Original PR description