openSUSE Build Service

opensuse.org · Storage · 1 record · JSON

openSUSE Build Service (OBS) - build.opensuse.org, public instance Storage

★ qualifiesinstitutionno cardRper-object-cap

build.opensuse.org · paas · storage/opensuse-build-service-build-opensuse-org-public-instanc · JSON · compare

Free tier	No published storage quota. The user guide states the instance 'can be used by anybody to freely create binaries for any of the supported distributions' and that 'You can store your sources there, build your packages and got them mirrored around the world.' The only quantitative ceilings found are per-file/per-build, not per-project: build disk constraint is expressed as `Constraint: hardware:disk:size unit=G <N>` and users are seen requesting 110 GB for one build (openSUSE forum, 2026-06-16). Observed real object size in the archive: `openSUSE:Factory/kernel-source/linux-7.2.tar.xz` is 160,068,116 bytes, served publicly. unit GB; metered on stored-bytes
Price	none stated
Per-object cap	per-object-cap: none documented for source blobs - 160 MB (160000000 bytes)
Retention	unpublished home projects are subject to admin cleanup, and binaries are pruned per repository/architecture
Egress	Free and mirrored: 'build your packages and got them mirrored around the world' - download.opensuse.org is a public mirror ring. No per-GB accounting, no billing relationship at all for the public instance.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: inux-7.2.tar.xz` is 160,068,116 bytes, served publicly. API source endpoint silently ignores Range and streams the whole object - will blow up any client that assumes 206. Home pr
Limits	per-object-cap per-object-cap: none documented for source blobs - 160 MB source per-object-cap: none documented for source blobs - 160 MB verified; unpublished home projects are subject to admin cleanup, and binaries are pruned per repository/architecture. IMPORTANT: Range requests are NOT honoured on the source endpoint (a bounded 1 MB range GET returned 200 with the full 160,068,116 bytes), so ranged/parallel fetch must be done against download.opensuse.org (mirror ring), not api.opensuse.org.
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, cli rest
Tooling	`osc` (CLI, in every openSUSE repo), OBS REST API (`api.opensuse.org/public/...` for anonymous reads, XML), and plain HTTPS download of published repositories from download.opensuse.org. `osc add $URL` stores a remote-source reference; `osc commit` uploads real blobs.
Composes with	unlimited home projects (`home:<user>:<sub>`) x unlimited packages per project x unlimited versions; published repos additionally replicate to every download.opensuse.org mirror at no cost. Sources are retained per package revision (the API exposes rev/vrev, e.g. osc 'rev=517 vrev=485'), so a single package with N commits holds N copies of the blob server-side. Multiply by unlimited free openSUSE accounts. This is the packaging-native equivalent of GitHub Releases, with a global mirror CDN attached.
Reliability	API source endpoint silently ignores Range and streams the whole object - will blow up any client that assumes 206. Home projects are explicitly deprioritised: 'home repos are by default low hanging fruit, other projects take priority'. Already documented in round 1's B-B5 dossier; recorded here only to note the 160 MB verified object and the no-Range behaviour.
Notes	No published storage quota. The user guide states the instance 'can be used by anybody to freely create binaries for any of the supported distributions' and that 'You can store your sources there, build your packages and got them mirrored around the world.' The only quantitative ceilings found are per-file/per-build, not per-project: build disk constraint is expressed as `Constraint: hardware:disk:size unit=G <N>` and users are seen requesting 110 GB for one build (openSUSE forum, 2026-06-16). Observed real object size in the archive: `openSUSE:Factory/kernel-source/linux-7.2.tar.xz` is 160,068,116 bytes, served publicly.
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 160.0 MB

Evidence (6)

date	source	what it proved
2026-10-21	api.opensuse.org/public/source/openSUSE:Factory/kernel-sourc	probe: GET -> 200 XML listing, entry linux-7.2.tar.xz size=160068116
2026-10-21	api.opensuse.org/public/source/openSUSE:Factory/kernel-sourc	probe: GET -> 200, content-length 160068116, application/octet-stream (real bytes, anonymous, no auth)
2026-10-21	withheld	probe: ranged GET bytes 0-1048575 on same URL -> 200 with 160068116 bytes (Range ignored)
2026-10-21	openbuildservice.org/help/manuals/obs-user-guide/cha-obs-bes	'You can store your sources there, build your packages and got them mirrored around the world.'
2026-10-21	forums.opensuse.org/t/disk-space-constraint/194432	2026-06 user sets `Constraint: hardware:disk:size unit=G 110` for a single build
2026-10-21	en.opensuse.org/openSUSE:Build_Service_Terms_of_Service	'You may not share API tokens to exceed OBS's rate limitations.'

Unknown or withheld values (4)

$.evidence[2].url private-url
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted

Built from commit 872967ae41, data as of 2026-10-27. Every value links to its source; freshness badges are computed in your browser. How to read this.