8000 1ES Pipeline Templates generates SBOMs for our SBOMs · Issue #1331 · dotnet/docker-tools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
1ES Pipeline Templates generates SBOMs for our SBOMs #1331
Open
@lbussell

Description

@lbussell

We compute and upload our container image SBOMs ourselves, and upload them as a pipeline artifact. 1ES pipeline templates also generates an SBOM for every pipeline artifact that's published. Thus, 1ES pipeline templates ends up generating a (useless) SBOM for our real SBOMs. The result is that it's difficult to traverse the pipeline artifacts and grab a useful SBOM. We should find a way to stop uploading these meta-SBOMs.

Example:

  • The sboms folder is what we upload.
  • It contains SBOMs for each of the images in its own folder.
  • 1ESPT injects the _manifest folder which contains the SBOMs for our SBOMs.

image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Current Release

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0