-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
Installer Sprint 2025-60
-
None
Value Statement
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.
Definition of Done for Engineering Story Owner (Checklist)
- The script outputs whether a PR is in a particular build
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- relates to
-
ACM-20994 As an engineer on the installer team, I want to enhance the QE downstream script to automatically check the latest downstream build
-
- Closed
-