Epic Goal

• Our current CI system does not test what is important in an acceptable amount of time, we would like to remedy that to improve the devex. Additionally, we would like the refactored system to allow developers to run a copy of the CI on their laptop.

Why is this important?

• See Combined CI/Testing Pain Points#State from end of February
•  

Scenarios

1. CI run on each PR to validate and test new code.
2. CI run on a schedule to exhaustively test code base.
3. CI run on developer's environment to test new code prior to submission of a PR.
   1. This environment should allow the developer to run debugging tools such as devl against artifact like podman.

Acceptance Criteria

• https://docs.google.com/document/d/1OXvtd45Lh86q-_ifqOFGQNrxS0RuhGpP3f7oqH9Gh54/edit#heading=h.oo2l947zkycx
•  

Dependencies (internal and external)

1. Will be determined by stories associated with this Epic.

Previous Work (Optional):

1. …

Open questions::

1. What kind of CI do the containers repositories and developers require to take Podman development and delivery to the next level?
2.  

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>