## Description There are well known change sets that don't get tested in the package pipelines, e.g. istio resources, kyverno policies, monitoring endpoints, etc. We know these should be tested before they get merged into the package repo and have [instructions on how to do that](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/docs/developer/test-package-against-bb.md?ref_type=heads). Right now the expectation is that the CODEOWNERS understand which change sets would need these tests and will prevent merges until those tests are complete. This could be improved with, at a minimum, an automated comment or other system that reminds the CODEOWNERS and assignee that those change sets have been modified and additional testing is required. ## Requirements/Scope - A way to define a/some changeset(s) that need additional testing - An automated system that will notify/require additional testing if an MR includes any changes in those pre-defined changesets - Optional: block MRs that need those tests until those tests pass - Optional: kick off those tests automatically if they are needed ## Out of Scope - Update the package pipelines to include integration testing ## Duration 2 weeks. ## Team Either Tooling & Automation, and/or a cross-functional team with people from every team. ## Epic Team Members TBD ## Dependencies N/A ## Risks - Scope Creep - Ambiguous requirements/acceptance criteria - Maintenance/upkeep costs ## Acceptance Criteria See [Requirements](https://repo1.dso.mil/groups/big-bang/-/epics/335#requirementsscope). ## Related Issues and/or Epics TBD