Artifact Cache

Accelerate your workflows with the Artifact Cache.

The BuildPulse cache seamlessly replaces GitHub’s cache action, providing faster and more reliable performance. Unlike GitHub's cache, which stores artifacts in Azure Blob Storage and may suffer from latency issues, the BuildPulse cache is co-located with BuildPulse Runners, minimizing network latency.

Usage

Switching from actions/cache to the BuildPulse cache requires replacing the actions/cache@v4 line in your workflows with buildpulse/cache@v4:

name: Cache dependencies
- uses: actions/cache@v4
+ uses: buildpulse/cache@v4
  with:
    key: ${{ runner.os }}-yarn-${{ hashFiles('./yarn.lock') }}
    path: ./node_modules

If you're currently using actions/cache/save or actions/cache/restore, update them to buildpulse/cache/save and buildpulse/cache/restore, respectively.

Refer to the GitHub repository for more technical documentation.

Cache Size and Pricing

Using the BuildPulse cache incurs no additional cost, no storage limits, and has a data retention policy of 14 days.

Language-specific Cache Actions

In addition to the general buildpulse/cache, BuildPulse provides optimized replacements for GitHub’s language-specific setup actions. These drop-in replacements offer the same functionality but leverage the improved performance of the BuildPulse cache:

• setup-go@v5
• setup-node@v4
• setup-python@v6
• setup-ruby@v2
• setup-java@v5

Example:

name: Setup Go
- uses: actions/setup-go@v5
+ uses: buildpulse/setup-go@v5
  with:
    go-version: '>=1.17.0'

Check the README files for each setup action for detailed configuration guidance. For languages not explicitly supported by our setup actions, you can still leverage buildpulse/cache by following our general caching guidelines.