Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: release assets for multiple platforms #434

Merged
merged 6 commits into from
Jan 7, 2023
Merged

chore: release assets for multiple platforms #434

merged 6 commits into from
Jan 7, 2023

Conversation

suzuki-shunsuke
Copy link
Contributor

@suzuki-shunsuke suzuki-shunsuke commented Jan 6, 2023

Copy link
Member

@ianlewis ianlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

permissions:
actions: read # For the detection of GitHub Actions environment.
id-token: write # For signing.
contents: write # For asset uploads.
uses: slsa-framework/slsa-github-generator/.github/workflows/[email protected]
with:
go-version: 1.18
config-file: .github/config-release.yml
config-file: .slsa-goreleaser-${{matrix.os}}-${{matrix.arch}}.yml
compile-builder: true
evaluated-envs: "VERSION:${{needs.args.outputs.version}}"

# In case this fails, e.g. build configuration changes, file an issue in slsa-verifier
if-failed:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@laurentsimon @asraa Do we even need this in the release workflow? It's not a pre-submit so I don't think we need it to create GitHub issues?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're right we can remove the if-failed. @suzuki-shunsuke please remove it and let's merge.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed. bec4a0b

@suzuki-shunsuke
Copy link
Contributor Author

I tested, then SLSA Provenance was created successfully.

The files were created per platform separately.

  • slsa-verifier-linux-amd64.intoto.jsonl
  • slsa-verifier-linux-arm64.intoto.jsonl

I think ideally Provenance files should be merged into one file multiple.intoto.jsonl.

@ianlewis
Copy link
Member

ianlewis commented Jan 6, 2023

I think ideally Provenance files should be merged into one file multiple.intoto.jsonl.

Yeah, ideally we'd do that but I think it's ok for now. See slsa-framework/slsa-github-generator#63

@suzuki-shunsuke
Copy link
Contributor Author

I added macOS and windows.

Copy link
Contributor

@laurentsimon laurentsimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! Looks great!

permissions:
actions: read # For the detection of GitHub Actions environment.
id-token: write # For signing.
contents: write # For asset uploads.
uses: slsa-framework/slsa-github-generator/.github/workflows/[email protected]
with:
go-version: 1.18
config-file: .github/config-release.yml
config-file: .slsa-goreleaser-${{matrix.os}}-${{matrix.arch}}.yml
compile-builder: true
evaluated-envs: "VERSION:${{needs.args.outputs.version}}"

# In case this fails, e.g. build configuration changes, file an issue in slsa-verifier
if-failed:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're right we can remove the if-failed. @suzuki-shunsuke please remove it and let's merge.

This job is unneeded anymore.

#434 (comment)

Signed-off-by: Shunsuke Suzuki <[email protected]>
permissions:
actions: read # For the detection of GitHub Actions environment.
id-token: write # For signing.
contents: write # For asset uploads.
uses: slsa-framework/slsa-github-generator/.github/workflows/[email protected]
with:
go-version: 1.18
config-file: .github/config-release.yml
config-file: .slsa-goreleaser-${{matrix.os}}-${{matrix.arch}}.yml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you move the config files into a new .goreleaser folder? Sorry, I did not catch this earlier. Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These configuration files are not for GoReleaser, so I prefer .slsa-goreleaser than .goreleaser.
How about .slsa-goreleaser/${{matrix.os}}-${{matrix.arch}}.yml?
What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved. 477c130

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants