{CI} Generate SBOM manifest for built packages #21278
Merged
Conversation
This file contains 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
wangzelin007
force-pushed
the
test-SBOM
branch
from
1cae6eb to
dabe7b6
Compare
wangzelin007
force-pushed
the
test-SBOM
branch
from
cc90a78 to
2e3a8e4
Compare
wangzelin007
force-pushed
the
test-SBOM
branch
from
68adc9c to
c31cc9f
Compare
|
CI |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
jiasli
approved these changes
Mar 4, 2022
|
PR title can be "Generate SBOM manifest for built packages". BTW, if anyone is interested, SBOM stands for "Software Bill of Materials". BTW No 2, it should be "manifest", not "mainfest". 🤣 |
wangzelin007
changed the title
jsntcy
reviewed
Mar 4, 2022
jsntcy
approved these changes
Mar 4, 2022
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.
Description
Add ado-sbom-generator-task to support Generate SBOM (Software Bill of Materials) manifest for built packages.
We need generate SBOM manifest in every artifacts directory.
But there are two remaining problems：
Open two issues in component-detection repo.
Component detection only find the setup.py file in tools directory.
Component detection only match setup.py and requirement.txt file.
Packaging.EnableSBOMSigning: trueis set.error message:
- ##[error]The signing feature is not available for your organization yet.Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change.[Component Name 2]
az command b: Add some customer-facing feature.This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.