Maxamillion (talk | contribs) (Created page with "= THIS PAGE IS A DRAFT = = Fedora Release Engineering = {{Anchor|Introduction}} == Fedora Release Tooling Overview == Fedora Release Engineering uses a number of tools that...") |
Maxamillion (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= THIS PAGE IS A DRAFT = | = THIS PAGE IS A DRAFT = | ||
{{Anchor|Introduction}} | {{Anchor|Introduction}} | ||
= Fedora Release Tooling Overview = | |||
Fedora Release Engineering uses a number of tools that are loosely coupled with one another in order to ultimately create consumable media, images, and packages. | Fedora Release Engineering uses a number of tools that are loosely coupled with one another in order to ultimately create consumable media, images, and packages. | ||
| Line 12: | Line 10: | ||
Below is an overview of some of the tooling and how it relates to one another: | Below is an overview of some of the tooling and how it relates to one another: | ||
== Rawhide Nightly == | |||
Fedora Rawhide Nightly composes are done using the [https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide buildrawhide] and [https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched buildbranched] scripts which set the stage for the execution of the [https://git.fedorahosted.org/cgit/releng/tree/scripts/build-functions.sh build-functions.sh] script. | Fedora Rawhide Nightly composes are done using the [https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide buildrawhide] and [https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched buildbranched] scripts which set the stage for the execution of the [https://git.fedorahosted.org/cgit/releng/tree/scripts/build-functions.sh build-functions.sh] script. | ||
| Line 19: | Line 17: | ||
Release composing is done via the [https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi run-pungi] script. | Release composing is done via the [https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi run-pungi] script. | ||
== Pungi == | |||
[https://fedorahosted.org/pungi Pungi] is the tool used to compose Fedora releases. It requires being ran in a chroot of the package set that it is composing. This ensures that the correct userland tools are used to match up with the kernel that will be used to perform the installation. It uses a comps file + yum repos to gather packages for the compose. The [[Koji]] build system provides a way to run tasks within chroots on the various arches, as well as the ability to produce yum repos of packages from specific collections. | [https://fedorahosted.org/pungi Pungi] is the tool used to compose Fedora releases. It requires being ran in a chroot of the package set that it is composing. This ensures that the correct userland tools are used to match up with the kernel that will be used to perform the installation. It uses a comps file + yum repos to gather packages for the compose. The [[Koji]] build system provides a way to run tasks within chroots on the various arches, as well as the ability to produce yum repos of packages from specific collections. | ||
Latest revision as of 20:01, 21 April 2015
THIS PAGE IS A DRAFT
Fedora Release Tooling Overview
Fedora Release Engineering uses a number of tools that are loosely coupled with one another in order to ultimately create consumable media, images, and packages.
Most of this page is dedicated to documenting the scripts used to automate processes help in the Fedora releng git repository.
Below is an overview of some of the tooling and how it relates to one another:
Rawhide Nightly
Fedora Rawhide Nightly composes are done using the buildrawhide and buildbranched scripts which set the stage for the execution of the build-functions.sh script.
Release Composing
Release composing is done via the run-pungi script.
Pungi
Pungi is the tool used to compose Fedora releases. It requires being ran in a chroot of the package set that it is composing. This ensures that the correct userland tools are used to match up with the kernel that will be used to perform the installation. It uses a comps file + yum repos to gather packages for the compose. The Koji build system provides a way to run tasks within chroots on the various arches, as well as the ability to produce yum repos of packages from specific collections.