Prerelease SBOM#51
Open
riley206-pnnl wants to merge 4 commits into
Open
Conversation
Author
|
fixes #31 |
Author
|
I need to look into this more. |
Author
|
Further testing was done. It is working as intended. It only runs when non doc changes occur. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds CycloneDX Software Bill of Materials (SBOM) generation to the shared VOLTTRON pre-release workflow.
Previously, the full-release workflow generated SBOM data, but the pre-release workflow only built and published Python distribution artifacts. As a result, pre-release GitHub releases did not include an SBOM.
Changes
cdxgen -t python .
Behavior
After this change, repositories using the shared deploy-pre-release.yml workflow will attach bom.json to every generated GitHub prerelease.
When depscan succeeds, its generated report files are also attached. If depscan fails because of its vulnerability-database infrastructure, the workflow logs the error and continues so the valid SBOM is still published.
Validation
Tested through the forked volttron-weather-dot-gov pre-release workflow.
The test created the GitHub prerelease v2.0.0rc1 and attached: