From Fedora Project Wiki
(→‎Goal: Update the goal)
(→‎More Details: Update scope section)
Line 11: Line 11:
 
'''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 will gate a broken combination of changes, or otherwise unacceptable set of changes (due to policy, schedule, etc.) from reaching users.
 
'''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 will gate a broken combination of changes, or otherwise unacceptable set of changes (due to policy, schedule, etc.) from reaching users.
  
=== More Details ===
+
=== Scope ===
  
TODO: Link to previous discussions.
+
During this objective, the focus and scope of CI will be on packages included in Atomic Host. These represent many of the core packages in Fedora.  
  
TODO: Link to test definitions.
+
In addition the delivery will be limited to composed artifacts of Atomic Host:
 +
 
 +
* QCow2 images
 +
* Vagrant images
 +
* OSTree trees
 +
* Amazon Public Cloud images
  
 
=== Deliverables ===
 
=== Deliverables ===

Revision as of 07:45, 2 July 2017

Objective: Deliver Fedora Atomic Host via CI/CD

Goal

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

A contintuous 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 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.

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 will gate a broken combination of changes, or otherwise unacceptable set of changes (due to policy, schedule, etc.) from reaching users.

Scope

During this objective, the focus and scope of CI will be on packages included in Atomic Host. These represent many of the core packages in Fedora.

In addition the delivery will be limited to composed artifacts of Atomic Host:

  • QCow2 images
  • Vagrant images
  • OSTree trees
  • Amazon Public Cloud images

Deliverables

TODO: Fill this section in.

The contents of Fedora Atomic Host should be consistent with previous releases.

Special Interest Group

TODO: Describe SIG

Objective Lead

Stef Walter

Timeframe

TODO: More details

Fedora Atomic 27

Describe Plan B around Atomic Host.

By Flock in September (also of this year), ...