CI provider
Cacheport with TeamCity
TeamCity agents build many projects and keep local caches, but new agents start cold and local caches do not travel. Cacheport shares packages and build outputs across every agent.
- Config
- .teamcity/settings.kts or UI
- Token
- Password parameter env.CACHEPORT_TOKEN
- Build cache
- Gradle and Bazel remote cache
- Agents
- Cloud and on-premises
Give your pipelines a token
Parameters named env.* become environment variables on the agent. Password parameters are masked in logs.
params {
password("env.CACHEPORT_TOKEN", "credentialsJSON:<token id>")
}Examples
Copy-ready configuration for common setups.
Gradle with build cache
object Build : BuildType({
name = "Build"
params {
password("env.CACHEPORT_TOKEN", "credentialsJSON:<token id>")
}
steps {
gradle {
tasks = "build"
}
}
})npm
echo "registry=https://acme.cacheport.cc/npm/" > .npmrc
echo "//acme.cacheport.cc/npm/:_authToken=${CACHEPORT_TOKEN}" >> .npmrc
npm ci
npm testGradle remote build cache
With the settings from the Gradle page, every agent reads and writes the same remote build cache, so a task compiled on one agent is reused on all others.
FAQ
Questions
Does it work with TeamCity Cloud?
Yes. Cloud agents reach Cacheport over HTTPS.
Can I keep agent-local caches?
Yes. Local caches still help on warm agents; Cacheport covers cold ones.
Where does the token live?
In TeamCity's secure token storage, referenced by the password parameter.
Other CI providers
Setting up somewhere else too?
Start on the free plan
20 GB of cache, every registry, unlimited users. Upgrade when your pipelines outgrow it.