Open Build Service target pinning for repeatable development environment packages

Goal is to use openSUSE Open Build Service to generate packages for a repeatable development environment across developer workstations and CI pipelines. OBS builds each target in a clean isolated build root per target, which limits dependency drift between environments.

Build reproducibility is not guaranteed by default. Timestamps, file ordering and embedded paths can differ between rebuilds of the same source. Selecting openSUSE Tumbleweed versus Leap as the OBS target is an unresolved version-pinning decision, because Tumbleweed rolls continuously while Leap is fixed. Publish and release actions move packages between repositories with non-instant metadata refresh, and identical source can resolve dependencies differently per target snapshot.

What documented controls exist to pin an OBS build to a specific distribution snapshot for long-term repeatability? In what ways does target choice between Tumbleweed and Leap affect dependency resolution stability over time? What repository pinning practices are supported to avoid breakage from staging or release metadata delays?