-
Story
-
Resolution: Done
-
Normal
-
None
-
None
Goal
When QE is validating merged Pull Requests on GitHub, the code changes are frequently not in the downstream build right away. I want to write a script that will make it easy for QE to know when a particular PR has made it into the downstream build to begin testing.
Why is this important?
Many times throughout a release, QE comes to the development team and asks if a particular PR has merged yet. Checking the commit history of a project and manually confirming commit shas is tedious and time consuming
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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)
- duplicates
-
ACM-24672 As an Installer def, I want to write a script to quickly alert my QE contact when my changes are in downstream builds ready for testing
-
- Closed
-