chia7712 commented on PR #17204: URL: https://github.com/apache/kafka/pull/17204#issuecomment-2371997066
Pardon me if I misunderstood, but I’m not entirely sure I grasp the use of either the floating tag or trunk-cached. From what I gather, the PR aims to provide a more developer-friendly way to display the cached reference. Developers should consider basing their PRs on the cached reference rather than trunk, as this can leverage the Gradle cache to speed up CI. I have two questions if the above description is correct. 1. The downside of basing a PR on a non-trunk branch is that the PR can become out of sync, potentially leading to compile error or failed tests. Additionally, writing code based on a specific cached reference isn’t as straightforward. While I understand the benefit of leveraging the Gradle cache, I’m uncertain if it's worth it and how we could effectively 'request' developers to follow this approach. 2. why not using the [GitHub cache APIs](https://docs.github.com/zh/rest/actions/cache?apiVersion=2022-11-28) to show the latest cached reference? for example: ``` jenkins@25d1ceb7ea06:~/repo$ curl -s "https://api.github.com/repos/apache/kafka/actions/caches?key=gradle-home-v1|Linux-X64|test" | grep "key" | cut -d- -f5 | cut -d'"' -f1 | head -n 1 1bd9dc3ffc78880923a2651aa005a8f564581f9a ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
