Welcome to Koji’s documentation!¶
Koji is the software that builds RPM packages for the Fedora project. It uses Mock to create chroot environments to perform builds. To download the source code, report bugs, join the mailing list etc., see the Koji project website.
- Koji HOWTO
- Access Controls
- Permission system
- Defining Hub Policies
- Koji Kerberos/GSSAPI debugging
- External Repository Server Bootstrap
- Building Images in Koji
- Building for Windows
- Exporting repositories
- How tag inheritance works
- Koji Miscellaneous Notes
- Release Notes
- Koji 1.28.1 Release notes
- Koji 1.28.0 Release notes
- Koji 1.27.1 Release notes
- Koji 1.27.0 Release notes
- Koji 1.26.1 Release notes
- Koji 1.26.0 Release notes
- Koji 1.25.1 Release notes
- Koji 1.25.0 Release notes
- Koji 1.24.1 Release notes
- Koji 1.24.0 Release notes
- Koji 1.23.1 Release notes
- Koji 1.23.0 Release notes
- Koji 1.22.1 Release notes
- Koji 1.22.0 Release notes
- Koji 1.21.1 Release notes
- Koji 1.21.0 Release notes
- Koji 1.20.1 Release notes
- Koji 1.20.0 Release notes
- Koji 1.19.1 Release notes
- Koji 1.19.0 Release notes
- Koji 1.18.1 Release Notes
- Koji 1.18.0 Release notes
- Koji 1.17.0 Release notes
- Koji 1.16.2 Release Notes
- Koji 1.16.1 Release Notes
- Koji 1.16.0 Release notes
- Koji 1.15.1 Release Notes
- Koji 1.15 Release Notes
- Koji 1.14 Release Notes
- Koji 1.13 Release Notes
- Migrating to Koji 1.28
- Migrating to Koji 1.27
- Migrating to Koji 1.26
- Migrating to Koji 1.25
- Migrating to Koji 1.24
- Migrating to Koji 1.23
- Migrating to Koji 1.22
- Migrating to Koji 1.21
- Migrating to Koji 1.20
- Migrating to Koji 1.19
- Migrating to Koji 1.18
- Migrating to Koji 1.17
- Migrating to Koji 1.16
- Migrating to Koji 1.15
- Migrating to Koji 1.14
- Migrating to Koji 1.13
- Migrating to Koji 1.12
- Migrating to Koji 1.11
- Migrating to Koji 1.10
- Migrating to Koji 1.9
- Migrating to Koji 1.8
- Migrating to Koji 1.7
- Koji CVEs
- Runs Here
- Koji Server Bootstrap
- Server How To
- Setting Up a Koji Build System
- Knowledge Prerequisites
- Package Prerequisites
- A note on filesystem space
- Koji Authentication Selection
- PostgreSQL Server
- Koji Hub
- Koji cli - The standard client
- Koji Web - Interface for the Masses
- Koji Daemon - Builder
- Kojira - Dnf|Yum repository creation and maintenance
- Bootstrapping the Koji build environment
- Minutia and Miscellany
- RPM Signing with Koji
- What is a GPG keypair?
- Inspecting an RPM signature
- Uploding signed RPMs to Koji
- Downloading a signed RPM from Koji
- Signing a build with multiple keys
- Creating repos of signed RPMs
- How to automate signing?
- Koji cryptography best-practices
- How do RPM signatures relate to HTTPS?
- How do RPM signatures relate to IMA signing?
- Database Howto
- kojid.conf Options
- Hub Configuration Options
- Using the koji build system
- Setting RPM Macros for Builds
- Koji Profiles
- Storage Volumes
- Writing Koji Code
- Koji Content Generators
- Koji Content Generator Metadata
- Unit tests in Fedora’s Jenkins
- Koji Utilities
- Supported Platforms
Setting up and using Koji on Fedora:
In Koji it is sometimes necessary to distinguish between a package in general, a specific build of a package, and the various rpm files created by a build. When precision is needed, these terms should be interpreted as follows:
The name of a source rpm. This refers to the package in general and not any particular build or subpackage. For example: kernel, glibc, etc.
A particular build of a package. This refers to the entire build: all arches and subpackages. For example: kernel-2.6.9-34.EL, glibc-2.3.4-2.19.
A particular rpm. A specific arch and subpackage of a build. For example: kernel-2.6.9-34.EL.x86_64, kernel-devel-2.6.9-34.EL.s390, glibc-2.3.4-2.19.i686, glibc-common-2.3.4-2.19.ia64
Quick overview of architecture and history is covered by Ken’s video.
Koji is comprised of several components:
koji-hub is the center of all Koji operations. It is an XML-RPC server running under mod_wsgi in Apache. koji-hub is passive in that it only receives XML-RPC calls and relies upon the build daemons and other components to initiate communication. koji-hub is the only component that has direct access to the database and is one of the two components that have write access to the file system.
kojid is the build daemon that runs on each of the build machines. Its primary responsibility is polling for incoming build requests and handling them accordingly. Essentially kojid asks koji-hub for work. Koji also has support for tasks other than building. Creating install images is one example. kojid is responsible for handling these tasks as well. kojid uses mock for building. It also creates a fresh buildroot for every build. kojid is written in Python and communicates with koji-hub via XML-RPC.
koji-web is a set of scripts that run in mod_wsgi and use the Cheetah templating engine to provide a web interface to Koji. It acts as a client to koji-hub providing a visual interface to perform a limited amount of administration. koji-web exposes a lot of information and also provides a means for certain operations, such as cancelling builds.
koji-client is a CLI written in Python that provides many hooks into Koji. It allows the user to query much of the data as well as perform actions such as adding users and initiating build requests.
kojira is a daemon that keeps the build root repodata updated. It is responsible for removing redundant build roots and cleaning up after a build request is completed.
As mentioned above, each tag has its own list of packages that may be placed in the tag. To see that list for a tag, use the list-pkgs command:
$ koji list-pkgs --tag dist-fc7 Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- ---------------- ElectricFence dist-fc6 pmachata GConf2 dist-fc6 rstrode lucene dist-fc6 dbhole lvm2 dist-fc6 lvm-team ImageMagick dist-fc6 nmurray m17n-db dist-fc6 majain m17n-lib dist-fc6 majain MAKEDEV dist-fc6 clumens [...]
The first column is the name of the package, the second tells you which tag the package entry has been inherited from, and the third tells you the owner of the package.
To see the latest builds for a tag, use the latest-build command:
$ koji latest-build --all dist-fc7 Build Tag Built by ---------------------------------------- -------------------- ---------------- ConsoleKit-0.1.0-5.fc7 dist-fc7 davidz ElectricFence-2.2.2-20.2.2 dist-fc6 jkeating GConf2-2.16.0-6.fc7 dist-fc7 mclasen ImageMagick-22.214.171.124-3.fc6.1 dist-fc6-updates nmurray MAKEDEV-3.23-1.2 dist-fc6 nalin MySQL-python-1.2.1_p2-2 dist-fc7 katzj NetworkManager-0.6.5-0.3.cvs20061025.fc7 dist-fc7 caillon ORBit2-2.14.6-1.fc7 dist-fc7 mclasen
The output gives you not only the latest builds, but which tag they have been inherited from and who built them (note: for builds imported from beehive the “built by” field may be misleading).
We’ve tried to make Koji self-documenting wherever possible. The command line tool will print a list of valid commands and each command supports –help. For example:
$ koji help Koji commands are: build Build a package from source cancel-task Cancel a task help List available commands latest-build Print the latest builds for a tag [...]
$ koji build --help usage: koji build [options] tag URL (Specify the --help global option for a list of other help options) options: -h, --help show this help message and exit --skip-tag Do not attempt to tag package --scratch Perform a scratch build --nowait Don't wait on build [...]
You can see administrator-only command help with –admin. Most users will never use these additional commands, but if you’re setting up your own Koji system, you may find them very useful.
$ koji help --admin Available commands: add-external-repo Create an external repo and/or add one to a tag add-group Add a group to a tag add-group-pkg Add a package to a group's package listing [...]
Koji is also known to be used in many places, and we track them on this page. Feel free to add your entry. There is no additional obligation to you for doing so. :)
Koji Contributor Guides¶
If you’re interested in submitting patches, writing documentation, or filing bugs this section is for you. In time this will be the best place to learn how to get involved.