Skip to content

Conversation

@onelapahead
Copy link

I found sometimes:

./gradlew spotlessApply --write-verification-metadata sha256

wasn't resolving all dependencies bc of how the build graph gets made for that command, so the bouncycastle module SHA wasn't included in the metadata file causing our internal Docker builds of Besu to fail.

So instead:

./gradlew :crypto:algorithms:compileJava --write-verification-metadata sha256

worked and downloaded the missing verifications. Going forward, we likely want to recommend to our devs to do:

 ./gradlew clean spotlessApply compileJava --write-verification-metadata sha256

in order to update the verification metadata.

Similarly, I found if I did:

 ./gradlew clean dependencies --write-verification-metadata sha256 --write-locks

It then generated the lockfiles for all the subprojects within Besu, which is likely what we want. Though its likely a lot more to maintain and use for SBOM generation.

Copy link

@matthew1001 matthew1001 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hopefully future PRs will just be small diffs on these new files :)

@matthew1001 matthew1001 merged commit ae1cc83 into kaleido-besu-release-25.8.0 Jan 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants