RUST-137 Add gradle/verification-metadata.xml for dependency verification#226
Conversation
Records SHA-256 checksums for all resolved dependencies, providing supply-chain guarantees. Also satisfies SonarQube rule S8569 which requires either gradle.lockfile or gradle/verification-metadata.xml next to each build.gradle.kts.
SummaryThis PR adds Gradle dependency verification via The PR also updates the build configuration to use SonarSource's Artifactory repository (repox.jfrog.io) for plugin resolution, and adds the Signature verification is disabled (checksums only), as noted in the author's description—this represents a common first-step setup before progressing to full signature validation. What reviewers should knowWhat to review:
Key details for reviewers:
|
Add pluginManagement in settings.gradle.kts and update buildSrc and e2e to resolve through repox first, following the same pattern as sonar-skunk. This ensures verification-metadata.xml checksums match on CI where all artifacts are fetched through repox.
The cross_platform_analyzers CI job has no Artifactory credentials, so plugins can only be resolved via Gradle Plugin Portal when repox returns 401.
|
romainbrenguier
left a comment
There was a problem hiding this comment.
That looks OK, but I think you need to verify the metadata and then change the "Generated by Gradle" to "Verified"





verify-signatures) left asfalse(checksums only, standard first-step setup)