m (Cverna moved page Changes/KonfluxFedoraCoreOS to Changes/KonfluxFedoraBootc: Change the title to be more generic) |
No edit summary |
||
Line 7: | Line 7: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= Using Konflux to build Fedora | = Using Konflux to build Fedora Bootc images <!-- The name of your change proposal --> = | ||
{{Change_Proposal_Banner}} | {{Change_Proposal_Banner}} | ||
Line 14: | Line 14: | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". --> | ||
The Fedora | The Fedora Bootc initiative would like to start using the Konflux platform to build to the Fedora Bootc images. | ||
The goal of this change is to deploy a instance of Konflux https://konflux-ci.dev/ in Fedora's infrastructure and start using it to build Fedora Bootc images. | |||
== Owner == | == Owner == | ||
Line 56: | Line 57: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
With the release of bootable containers, it is now possible to use the container build and release infrastructure for ostree editions. Fedora | With the release of bootable containers, it is now possible to use the container build and release infrastructure for ostree editions. Fedora Bootc would like to make use of these capabilities and start to migrate to Konflux. The scope of this change for the Fedora 42 timeline is: | ||
# Get Konflux deployed in Fedora Infrastructure (we need help from Fedora Infra as well as the Konflux team). | # Get Konflux deployed in Fedora Infrastructure (we need help from Fedora Infra as well as the Konflux team). We need support for x86, aarch64, ppc64le and s390x architectures. | ||
# Integrate Konflux with Fedora Account System and create a namespace for Fedora | # Integrate Konflux with Fedora Account System and create a namespace for Fedora Bootc. | ||
== Feedback == | == Feedback == | ||
Line 96: | Line 95: | ||
# This will introduce Konflux in Fedora's infrastructure and allow contributors to become more familiar with the platform. | # This will introduce Konflux in Fedora's infrastructure and allow contributors to become more familiar with the platform. | ||
# This will allow for Fedora | # This will allow for Fedora Bootc to be easier to customize, the build becomes a simple container build and contributors can easily duplicate the pipeline in Konflux. | ||
== Scope == | == Scope == |
Latest revision as of 12:00, 25 June 2024
Using Konflux to build Fedora Bootc images
Summary
The Fedora Bootc initiative would like to start using the Konflux platform to build to the Fedora Bootc images. The goal of this change is to deploy a instance of Konflux https://konflux-ci.dev/ in Fedora's infrastructure and start using it to build Fedora Bootc images.
Owner
- Name: Clément Verna
- Email: <cverna@fedoraproject.org>
Current status
- Targeted release: Fedora Linux 42
- Last updated: 2024-06-25
- [Announced]
- [<will be assigned by the Wrangler> Discussion thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
With the release of bootable containers, it is now possible to use the container build and release infrastructure for ostree editions. Fedora Bootc would like to make use of these capabilities and start to migrate to Konflux. The scope of this change for the Fedora 42 timeline is:
- Get Konflux deployed in Fedora Infrastructure (we need help from Fedora Infra as well as the Konflux team). We need support for x86, aarch64, ppc64le and s390x architectures.
- Integrate Konflux with Fedora Account System and create a namespace for Fedora Bootc.
Feedback
Benefit to Fedora
- This will introduce Konflux in Fedora's infrastructure and allow contributors to become more familiar with the platform.
- This will allow for Fedora Bootc to be easier to customize, the build becomes a simple container build and contributors can easily duplicate the pipeline in Konflux.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
Early Testing (Optional)
Do you require 'QA Blueprint' support? Y/N
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)