Add workflow to generate and upload SBOMs for new releases #1074
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to bootstrap the EF Security Team initiative of supporting projects in implementing automated SBOM generation and upload workflows, with the goal of enhancing software supply chain security.
We wanted this to seamlessly integrate with your existing release processes, so we implemented 1 workflow meant to generate an SBOM for the paho.mqtt.java product.
Currently the workflow is triggered by new releases being published. A maven cyclonedx plugin (cyclonedx-maven-plugin) is used to generate the SBOM, which is then uploaded as an artifact. The "store-sbom-data" reusable workflow stores additional metadata about the project and upon completion, the self service system downloads the SBOM from artifacts and uploads it to our DependencyTrack instance.
We have tested the SBOM generation separately and everything worked successfully. However, due to limited permissions and inability to simulate the trigger event, if the changes get merged, we'd ask if you could manually run it once so we can confirm the upload to our instance works as expected (for the version input feel free to use the existing latest tag).
Otherwise however feel free to update the workflow as needed, edits by maintainers are enabled. Please let us know if you have any questions we can help with.
used to sign the CLA) Hint: use the -s argument when committing.
you are fixing straight away that you add some Description about the bug and how this will fix it.