Http Cache Server / Gradle Remote Build Cache


I’m currently evaluating GitLab for a Gradle-based project. The caching layer currently focuses on zipping/unzipping contents from the various jobs. Gradle goes a step further by allowing the use of remote build caches (from Gradle itself, artifactory, etc.). Is there a recommended setup or any plans in this area? Gitlab already provides Maven and Docker repository to store artifacts. In this case a more generic HTTP repository would be helpful to have. The end result would be something much more fine-grained and transparent to the user:

  • no need to declare what needs caching
  • pipeline parts fetch what is actually necessary to do their job
  • concurrent runners do not override results and can share cached artifacts.

Regards Remo