Getting Started
What this action does, how to add it to a workflow, and how it works under the hood.
IMPORTANT: Developer documentation for the current development branch. This content is unreleased, may change without notice, and must not be treated as Buildish release documentation.
User Guide
How to use Buildish Mammoth Cache for Gradle and Maven in your workflows.
This section covers everything you need to integrate Mammoth Cache into your GitHub Actions workflows — from a first working snippet to distributed multi-job topologies, full configuration reference, cache-partition tuning, and security considerations.
The action ships in two build-tool-specific flavours that share the same two-phase prepare/finalize design and most configuration options:
- Gradle — adds secure wrapper JAR provisioning and caches
GRADLE_USER_HOME. - Maven — caches the Maven local repository (
~/.m2by default).
Start with Getting Started if you are new to the action, or jump directly to Configuration for a full input reference.
Single-Job Builds
Using Buildish Mammoth Cache in a workflow with a single build job.
Configuration Reference
All action inputs and config-file options for Buildish Mammoth Cache for Gradle and Maven.
Distributed Multi-Job Builds
How to use the distributed worker/aggregator mode to cache builds that run as multiple parallel jobs.
Cache Partitions
Built-in partitions, customization, glob rules, timestamp garbage collection, and restore cleanup for Buildish Mammoth Cache for Gradle and Maven.
Security
Required permissions, wrapper verification, token scoping, and hard cache exclusions for Buildish Mammoth Cache for Gradle and Maven.
Troubleshooting
Diagnostic steps for the most common problems with Buildish Mammoth Cache for Gradle and Maven.
Maven Caching Patterns
How to get the most out of Maven caching — what is portable in the local repository, why certain files are excluded, and how to structure workflows for maximum cache effectiveness.