[jira] [Resolved] (KAFKA-17479) Utilize Gradle build cache on GitHub CI

["David Arthur (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-17479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Arthur resolved KAFKA-17479.
----------------------------------
    Resolution: Fixed

This has been done for a while now

> Utilize Gradle build cache on GitHub CI
> ---------------------------------------
>
>                 Key: KAFKA-17479
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17479
>             Project: Kafka
>          Issue Type: Improvement
>          Components: build
>            Reporter: David Arthur
>            Assignee: David Arthur
>            Priority: Major
>
> In order to speed up our PR builds, we can make use of the Gradle build cache in conjunction with the GitHub action cache service. The goal of this ticket is to reduce the amount of redundant testing executed on PRs builds. This will speed up the feedback time for developers and reduce the resource consumption of Kafka CI from ASF's infrastructure.
> Some immediate benefits of the setup-gradle action include caching of:
>  * The Gradle distribution and wrapper
>  * The various JDKs we use
>  * The project dependencies
>  * Other Gradle runtime dependencies
> By explicitly enabling the Gradle build cache (with --build-cache), we can also have the outputs of our tasks cached between CI runs. This will allow us to only run tests for affected modules. 
>  
> Resources:
>  * [https://docs.gradle.org/current/userguide/build_cache.html]
>  * [https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#caching-build-state-between-jobs]
>  * [https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows#about-caching-workflow-dependencies]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)