#133 New Objective: Continuous Integration and Delivery of Fedora Atomic Host
Closed: approved 6 years ago Opened 6 years ago by stefw.

The CI WG and Atomic SIG want to propose an objective for Fedora:

http://fedoraproject.org/wiki/Objectives/Continuous_Integration_and_Delivery_of_Fedora_Atomic_Host

Summary:

We aim to deliver Atomic Host in Fedora via Continuous Integration and Continuous Delivery.

A continuous integration pipeline builds and composes Fedora Atomic Host artifacts exactly as they will be delivered and used (eg: in QCow2 and OSTree formats), and runs integration tests on it in that form.

Continuous integration pipeline will gate changes to packages. It will prevent a broken package change, as defined by integration tests, from affecting other developer's and/or testers of Fedora. The package maintainer will be able to change the tests on which their package is gated. The pipeline also gates broken combinations of package changes.

Continuous delivery will deliver the artifacts composed during integration step above to users of Fedora Atomic Host. It allows, but does not mandate constant or frequent delivery of changes to the Fedora mirrors. During delivery we can prevent unacceptable changes, due to policy or schedule, from reaching users.


This looks awesome to me. I love the specific numbers in the "Key results" section.

+1

+1 with the caveat that I'd like the proposal to identify who the working group would like to have been the objective lead representative to the council. I would prefer to have a specific person specified who can on occasion send a representative in their place, not a rotating group or a "one of the following ..." list.

+1 with @bex 's caveat to have a single PoC.

I am +1 with the caveat mentioned by @bex

@stefw @dustymabe — this is approved assuming you can pick one of you to be the Council lead.

I'm willing to standup and be i the Objective lead and work in the Fedora Council to achieve this.

Awesome. Thanks Stef and welcome to the Fedora council!

Metadata Update from @mattdm:
- Issue close_status updated to: approved
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata