CI providers
Works with the CI you already run
Cacheport is an HTTPS endpoint, so any CI system can use it. These guides cover storing the token, keyless sign-in where the CI supports it, and copy-ready examples.
CI.github/workflows/*.ymlGitHub ActionsSecrets or OIDC, setup-* actions and a cache that survives runner churn.Setup guide →CI.gitlab-ci.ymlGitLab CICI/CD variables, shared or self-managed runners, Docker executor.Setup guide →CI.circleci/config.ymlCircleCIContexts for tokens, convenience images and parallel jobs.Setup guide →CIJenkinsfileJenkinsCredentials binding and agents behind your own firewall.Setup guide →CIpipeline.ymlBuildkiteSelf-hosted agents at scale, one cache for the whole fleet.Setup guide →CIbitbucket-pipelines.ymlBitbucket PipelinesRepository variables and Docker-based steps.Setup guide →CIazure-pipelines.ymlAzure PipelinesVariable groups, Microsoft-hosted and self-hosted agents.Setup guide →CI.teamcity/settings.ktsTeamCityParameters and build agents with a shared remote cache.Setup guide →
Start on the free plan
20 GB of cache, every registry, unlimited users. Upgrade when your pipelines outgrow it.