koji-buildinfo

Print basic information

$ koji buildinfo [BuildID_or_NVR1 BuildID_or_NRV2 ...]

$ koji buildinfo [BuildID_or_NVR1 BuildID_or_NRV2 ...] --changelog

$ koji buildinfo [-h|--help]

koji buildinfo [COMMON_OPTIONS] <build_identifier>
build_identifier: Koji build ID (integer) or Name-Version-Release (NVR) string.
COMMON_OPTIONS: Standard koji client options applicable to most commands.

<build_identifier>
    The mandatory identifier for the build to query. This can be either the numeric Koji build ID (e.g., 12345) or a Name-Version-Release (NVR) string (e.g., my-package-1.0-1.fc34).

-h, --help
    Show the program's help message and exit. This will display general koji client options and a brief usage for buildinfo.

--config=FILE
    Specify an alternate configuration FILE for the koji client instead of the default ~/.koji/config or /etc/koji.conf.

--hub=URL
    Connect to a specific Koji hub at the given URL, overriding the configured default.

--weburl=URL
    Specify the base URL for the Koji web interface associated with the hub, primarily for informational purposes or to generate links.

--debug
    Enable debug logging, providing more detailed output useful for troubleshooting connection issues or unexpected behavior.

-q, --quiet
    Suppress most output, showing only critical messages or errors.

-v, --verbose
    Increase verbosity of the output, providing more detailed status messages.

--timeout=SECONDS
    Set a network timeout in SECONDS for operations, preventing indefinite hangs on unresponsive servers.

--authtype=TYPE
    Specify the authentication TYPE to use (e.g., kerberos, ssl). This is crucial for accessing protected hubs or privileged information.

The koji-buildinfo command (or more commonly invoked as koji buildinfo) is a fundamental utility within the Koji build system client, primarily used for retrieving comprehensive details about a specific build. Koji itself is a powerful, open-source build system developed by Red Hat, widely adopted for building RPM packages for Fedora, Red Hat Enterprise Linux, and other distributions.

This command provides a detailed snapshot of a build identified either by its unique numeric ID or its Name-Version-Release (NVR) string. The information displayed typically includes vital metadata such as the build ID, package name, version, release, current state (e.g., complete, failed), owner, creation and completion timestamps, associated build target and tags, and a list of all RPM packages produced by that build. It also provides details about the build source, such as the Git repository and commit hash.

Its primary use cases involve debugging build failures, verifying build provenance, auditing components, and understanding the lifecycle of a specific software build within the Koji infrastructure. It's an essential tool for developers, release engineers, and quality assurance teams working with Koji.

Requires network connectivity to a running Koji hub. The level of detail and access to sensitive build information might depend on the user's authentication and permissions configured on the Koji hub.
The command's output is typically human-readable plain text, which can be verbose and may require text processing tools like grep or awk for programmatic extraction of specific fields, as it does not inherently offer structured output like JSON or XML.

The output typically provides a human-readable, multi-line display of various build attributes, including identification, state, timestamps, associated packages (RPMs), build target, and source information. It's primarily designed for direct inspection rather than programmatic parsing, though basic text processing can extract specific fields.

The <build_identifier> argument is flexible, accepting either a numeric Koji build ID (e.g., 12345) or a Name-Version-Release (NVR) string (e.g., my-package-1.0-1.fc34). Using an NVR allows specifying a particular build of a package without prior knowledge of its internal ID, which is often convenient.

The Koji build system was initiated at Red Hat to streamline the build process for Fedora and later Red Hat Enterprise Linux. As a core client component, koji buildinfo has been integral since the early development of the Koji client, serving as a primary interface for querying build metadata. Its design reflects the need for immediate, detailed introspection into the state and provenance of software packages within a robust build environment. The command has evolved primarily through enhancements to the underlying Koji API and client infrastructure rather than significant changes to its fundamental function or syntax.

koji(1): The main Koji client command, providing access to a wide range of build system functions., koji list-builds(1): Lists builds based on various criteria (e.g., package, tag, state)., koji latest-build(1): Retrieves information about the most recent successful build for a given package., rpm(8): The standard Linux package manager, relevant for understanding the packages produced by Koji builds.