Epic Goal

The canary tests that ACM used to have were integrated into the build system and provided valuable feedback about what builds could be used.  The konflux pipelines should be able to drive an integrated experience that can deliver the same information about the builds that we used to have.

Why is this important?

1. How can Konflux accelerate our deliveries? Can we automate more things inside it, like BVT tests in IntegrationTestScenarios?
2. Re enable canary build tests. These were disabled with the konflux migration.  The QE/Jenkins tests are similar but don't run as often and don't have the same visibility.

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)