obtainbuild

Obtainbuild is a term used to describe a class of build automation tools that fetch source code from version control systems, resolve dependencies, and compile software within reproducible build environments. The aim is to produce artifacts that can be recreated exactly on different machines and at different times, supporting auditability, traceability, and reliable CI workflows.

Core concepts typically include a declarative manifest that lists sources, build steps, and environment requirements. The manifest may specify VCS repositories (Git, Mercurial, Subversion), pinned revisions or checksums, and the sequence of commands to execute. Build environments are commonly containerized or sandboxed to isolate dependencies and ensure determinism.

Key features commonly associated with obtainbuild-like tools include dependency resolution, caching of fetched sources and intermediate artifacts, parallelized builds, and provenance metadata such as compiler versions and dependency graphs. Many implementations integrate with continuous integration systems, provide logs and artifacts, and support reproducible packaging and signing.

Usage typically involves creating a manifest file, initializing a workspace, and running a single command to fetch sources, install dependencies, and execute the build steps. Artifacts are collected in a designated output directory and can be archived, signed, or published to artifact repositories.

Relation to other tools: Obtainbuild shares goals with other reproducible-build ecosystems such as Nix, Guix, Spack, and Bazel, each offering different approaches to isolation and dependency management. As a general concept, obtainbuild informs best practices for reproducible software builds in research, development, and CI environments.