Epic Goal

• As an Agent team member, I need a stable CI so that I can test and merge my work quickly and easily.

Why is this important?

• …

Scenarios

1. ...

Acceptance Criteria

• Review / Investigate what is causing CI to break
• Internal
  • Create more debug information to help with troubleshooting
  • Break down CI into smaller components to allow addition of failure conditions
• External
  • Work with others to determine how often tests run and request changes as necessary
  • For items which have been consistently broken, reach out to ART to get tests adjusted to be optional
  •  
• Prioritize and add current backlog items to CI Coverage in every sprint

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 - Downstream documentation merged: <link to meaningful PR>