ci: generate sboms for provided packeges in a release #247
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
y-eight
requested review from
niklastreml,
puffitos and
lvlcn-t
as code owners
|
LGTM but why is the syft installation needed in the e2e testing workflow? EDIT: I guess it's based on when we use the gorelease action, right? |
puffitos
requested changes
Jan 3, 2025
puffitos
reviewed
Jan 3, 2025
Correct! Syft is needed see this previous failing ci job: https://github.com/telekom/sparrow/actions/runs/12596763639/job/35108497305#step:4:1 |
puffitos
requested changes
Jan 20, 2025
puffitos
approved these changes
Jan 20, 2025
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.
Motivation
Goreleaser provides the functionality to generate the
sbomwhen creating a GitHub release with its artifacts.Changes
This MR will add
sboms for all provided artifacts when a new release is created. This is needed to prepare the migration of the repo.Edit: Additionally I have added a description how to use Syft manually in our context.
For additional information look at the commits.
Tests done