oscerd opened a new pull request, #4461: URL: https://github.com/apache/camel-quarkus/pull/4461
Signed-off-by: Andrea Cosentino <[email protected]> <!-- Uncomment and fill this section if your PR is not trivial [x] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [x] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #. [x] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [x] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [x] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request. [x] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html --> Fixes #4459 So this is a first iteration for having a SBOM for Camel-Quarkus. Generation time on a free repository: 41 minutes for me. SBOM dimensions: Around 8 MB My proposal: - In Camel we have a github action running every Sunday at 14:30. The action will rebase on particular branch "regen_bot_sbom", run the sbom generation, commit and create a PR with the SBOM updated. For the moment, the camel-sbom on Camel and camel-quarkus-sbom are not part of release process, so there want be an artifact for them. They are descriptors more or less. Let me know what you think and if you have proposals/doubts/discussions. Thank you -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
