How might we enhance validation on BOMs? #5922
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
There were problems in the entries in the gapic-libraries-bom ( googleapis/google-cloud-java#9304) protobuf-bom (protocolbuffers/protobuf#12170). The challenge is that Maven's build lifecycle does not invalidate bad entries in a BOM.
How might we enhance validation on BOMs? Especially those that are in different location than this java-cloud-bom repository.
Create Github Actions (a composite action)
In GitHub Actions, we can easily reference a check in another repository.
https://github.com/googleapis/google-api-java-client-services/blob/main/.github/workflows/codegen.yaml#L48
A composite action (https://docs.github.com/en/actions/creating-actions/creating-a-composite-action) is a good fit for the tasks below.
Implementation: a composite action
Before running the composite action the caller (gapic-generator-java or google-cloud-java repository) needs to make the BOM and its contents available in Maven Central or local Maven repository.
The action takes BOM coordinates as an argument.
The action does the followings:
mvn install
in the project to confirm the project is built.The text was updated successfully, but these errors were encountered: