Configuring the Build Cache for Gradle in non-Bitrise CI environments

The Bitrise Build Cache does not require using the Bitrise CI. You can use other CI/CD services and still take advantage of the cache to improve your Gradle build times.

To do so, you need to configure your CI environment to download the Bitrise Build Cache CLI during the build and then run the CLI to enable the Bitrise Build Cache.

You can also set this up with an AI coding agent instead of following the steps manually. See Getting started with AI.

Using GitHub Actions?

There is a dedicated guide with GitHub Actions workflow examples: Configuring the Build Cache for Gradle in GitHub Actions.

1. Select your Bitrise workspace and go to Build Cache.

2. Click New connection.

3. Select Other CI provider and then select your build tool from the dropdown menu.

   

4. Click Create token.

   

5. Enter a name and set it to never expire.

6. Copy the variables and add them to your CI configuration as Environment Variables.

7. Add the following script to your CI configuration before the step you want to speed up:

   Environment

   Make sure to run the script in the same environment as the Gradle command(s) you want to speed up. For example, if you use multiple Docker containers throughout the build, make sure that the Bitrise Build Cache CLI runs in the same Docker container as the Gradle command.

   #!/usr/bin/env bash
   set -euxo pipefail
   
   # download Bitrise Build Cache CLI
   curl --retry 5 -sSfL 'https://raw.githubusercontent.com/bitrise-io/bitrise-build-cache-cli/main/install/installer.sh' | sh -s -- -b /tmp/bin -d
   
   # run the CLI to enable Bitrise build cache for Gradle
   /tmp/bin/bitrise-build-cache activate gradle --cache --cache-push