[7.2] Use Gradle's Build Cache alongside in-house caching

Open
#993 1 comment 0 reactions 1 assignee View on GitHub

@Jonathing is already working on this.

Since Oct 8, 2025.

Assessment

This issue has not been assessed yet.

Description

Gradle's Build Cache is Gradle's caching solution for tasks (and other work types, such as artifact transforms).

Implementing support for Gradle's own build cache will take significantly more work than supporting the configuration cache (#992) or configuration on demand (#991), but is something we should look into to maximize the performance gains that ForgeGradle 7 can handle.

In terms of support, ForgeGradle 7 has support for build caching being enabled, but it itself does not use the build cache for any of its tasks or executions. Additionally, projects we should look into working in Gradle Build Cache support for will include AccessTransformers Gradle, JarJar Gradle, and the Obfuscation plugin (yet to be made), as they provide UserDev transforms and tasks respectively.

This issue will be closed once ForgeGradle 7 and/or all of its sister plugins have implemented sufficient support for Gradle Build Cache.

cc @LexManos @PaintNinja @mezz

Dominant language
Java
Stars
574
Forks
450
Avg merge
16h 20m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MinecraftForge/ForgeGradle

All issues in MinecraftForge/ForgeGradle

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.