Agree on a standard common definition of the build matrix for Oniro, blueprints and OpenHarmony
Value
Having a standard way of defining of the build matrix across the multiple projects of the Oniro "family" (i.e. Oniro, blueprints, OpenHarmony), which could be used both by test/build pipelines and by compliance pipelines, so that possible changes in the matrix are automatically reflected in all pipelines without the need of (error-prone) manual intervention
Acceptance Criteria
Standard definition of the build matrix with all the relevant variables that are needed to uniquely identify each target
Applicable Personas
- License Compliance Auditor