JitPack

jitpack.io · Storage · 1 record · JSON

JitPack (jitpack.io) - build-on-demand Maven from git Storage

fails: quotainstitutionno cardRper-object-cap

jitpack.io · registry · storage/jitpack-build-on-demand-maven-from-git · JSON · compare

Free tier	Bounded by the size of the git repo it builds from, not by a storage quota: a build fails with 'Git error. Max repo size 250MB exceeded'. JitPack builds any public git repo on demand and serves the resulting Maven artifacts at com.github.<user>.<repo>:<tag>. unit mixed; metered on stored-bytes
Price	none stated
Per-object cap	per-object-cap: 250 MB (250000000 bytes)
Retention	not stated
Egress	Free. Artifacts served from jitpack.io CDN with no billing.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: ard-capped at 250 MB. Read path live and public (verified /api/builds/com.github.jitpack/maven-simple returning ok states across dozens of tags). unlimited public git repos x unlimit
Limits	per-object-cap per-object-cap: 250 MB source per-object-cap: 250 MB repo size (hard build error). request-rate: builds are queued per-IP (anonymous builds are rate limited; the API exposes per-tag build state). retention: build artifacts are cached but a failing/expired build is rebuilt on demand - not durable storage.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, rclone, cli rest
Tooling	Any Maven/Gradle resolver pointed at https://jitpack.io; JitPack build API at /api/builds/<group>/<artifact> (open, returns build status per tag). No dedicated CLI beyond Maven/Gradle; no rclone backend.
Composes with	unlimited public git repos x unlimited tags/commits x 250 MB repo each. Because artifacts are derived, storage is the repo's, and the same content is rebuilt per tag - so it amplifies, it does not multiply storage. 250 MB x N repos is the honest ceiling.
Reliability	Build service, not storage: artifacts can be evicted and rebuilt, and repo size is hard-capped at 250 MB. Read path live and public (verified /api/builds/com.github.jitpack/maven-simple returning ok states across dozens of tags).
Notes	Bounded by the size of the git repo it builds from, not by a storage quota: a build fails with 'Git error. Max repo size 250MB exceeded'. JitPack builds any public git repo on demand and serves the resulting Maven artifacts at com.github.<user>.<repo>:<tag>.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 250.0 MB

Evidence (3)

date	source	what it proved
2026-10-21	github.com/jitpack/jitpack.io/issues/4898	'Build issue Max repo size 250MB exceeded'; 'Git error. Max repo size 250MB exceeded'
2026-10-21	jitpack.io/api/builds/com.github.jitpack/maven-simple	probe: GET -> 200 JSON, dozens of tag/commit entries with status 'ok'
2026-10-21	docs.jitpack.io/building/	build-on-demand model

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "Bounded by the size of the git repo it builds from, not by a storage quota: a build fails with 'Git error. Max repo size 250MB exceeded'. JitPack builds any public git repo on demand and serves the resulting Maven artifacts at com.github.<user>.<repo>:<tag>.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (5)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted