Koji/Repositories

Koji maintains repositories of various content types to assist with quickly creating consistent build environments. This page assumes you have read the The supported content types today are:

• RPMs (via yum repositories)
• Java Artifacts (via Maven repositories)

All repositories are kept under the /mnt/koji/repos directory on shared storage. They are maintained by the **Kojira** service, which is responsible for regenerating them as needed when the content of a build tag changes (including inheritance changes), and for deleting them when they become stale.

All repositories are associated with a (build) tag, which in turn is associated with a target. Therefore, all Koji targets have a

Kojira is a standard service that can be started and stopped as necessary, but leaving it running is the recommended practice. Configuration is controlled in the /etc/kojira/kojira.conf. Like the other Koji services it needs auth configuration set up before it can function, and details about that are in the Run Your Own Koji Build Server page. The two options we will cover here control the lifetimes of the repositories.

deleted_repo_lifetime signed_repo_lifetime

Yum Repositories

Koji maintains yum repositories