cacheport

CI provider

Cacheport with Bitbucket Pipelines

Every Bitbucket Pipelines step runs in a fresh container. Store a Cacheport token as a secured variable and steps pull packages and images from a regional cache.

CI · BITBUCKET-PIPELINESManifest
Config
bitbucket-pipelines.yml
Token
Secured workspace variable CACHEPORT_TOKEN
Images
Step images through the image cache
Caches
Built-in caches still work alongside

Give your pipelines a token

Add a secured variable

Workspace variables are available to every repository in the workspace.

shell
$ cacheport token create bitbucket --scope read
# Bitbucket: Workspace settings > Workspace variables
# Name: CACHEPORT_TOKEN  Secured: yes

Examples

Copy-ready configuration for common setups.

npm

bitbucket-pipelines.yml
image: node:22
pipelines:
  default:
    - step:
        name: Test
        script:
          - echo "registry=https://acme.cacheport.cc/npm/" > .npmrc
          - echo "//acme.cacheport.cc/npm/:_authToken=${CACHEPORT_TOKEN}" >> .npmrc
          - npm ci
          - npm test

Step image from the cache

bitbucket-pipelines.yml
image:
  name: acme.cacheport.cc/hub/library/python:3.13
  username: ci
  password: $CACHEPORT_TOKEN
pipelines:
  default:
    - step:
        script:
          - pip install -r requirements.txt
          - pytest

Questions

Should I keep the built-in caches?

Yes. They save the copy step on a hit; Cacheport makes misses fast.

Does it work with self-hosted runners?

Yes, as long as the runner can reach acme.cacheport.cc over HTTPS.

Are step images cached too?

Yes, when you reference them through acme.cacheport.cc/hub/ with credentials as shown.

Setting up somewhere else too?

Start on the free plan

20 GB of cache, every registry, unlimited users. Upgrade when your pipelines outgrow it.