mumrah commented on PR #17204: URL: https://github.com/apache/kafka/pull/17204#issuecomment-2372242688
@chia7712 > Developers should consider basing their PRs on the cached reference rather than trunk, as this can leverage the Gradle cache to speed up CI. Yes, this is the main idea here. During busy times when trunk is changing multiple times per day, it will commonly be the case that trunk will be ahead of the cache (since the CI job will be running). So, a developer merging trunk into their branch will be pulling in new changes that aren't in the cache yet. I imagine the workflow changing from: ``` git fetch origin git merge origin/trunk // resolve conflicts git push mumrah my-branch ``` to this ``` git fetch origin git merge origin/trunk-cached // resolve conflicts git push mumrah my-branch ``` 1. Ideally, the "cached" tag/branch will only be a small number of commits behind trunk. We can advertise this feature in the pull request template. It's not a perfect solution, but for committers (who make lots of changes), we can benefit from fewer cache misses. 2. Do you mean, developers can use this to find the latest cached SHA when merging/rebasing? -- 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]
