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

Provide checksums of or sign releases #2796

Open
RemcodM opened this issue May 27, 2024 · 1 comment
Open

Provide checksums of or sign releases #2796

RemcodM opened this issue May 27, 2024 · 1 comment

Comments

@RemcodM
Copy link
Contributor

RemcodM commented May 27, 2024

Is your feature request related to a problem? Please describe.
For more automation in our workflow of updating our infrastructure with the newest Buildkite Agents, we would like to automatically check the integrity of the downloaded artifacts.

Describe the solution you'd like
It seems that in the past, it might have been possible to get sha256 sums via #500, however, this does not seem to be possible anymore (or is it?). Something like providing checksums would already be sufficient, even nicer would it be if the builds could be signed, for example using PGP.

Describe alternatives you've considered
At this point, we calculate the checksums ourselves to ensure that the artifacts doesn't change from build to build, but that is a lot of manual work that is almost impossible to automate correctly. Provided checksums also give more confidence that the artifact was uploaded correctly from your side.

Additional context

@DrJosh9000
Copy link
Contributor

Hi @RemcodM ! Thanks for raising this. Making verifying agent binaries easier is something that's been on our mind for a while and we'd like to make it better. I think we could easily add a "sha256sums" file to each release.

The checksum files in #500 should still be updated too, e.g.:

https://download.buildkite.com/agent/stable/latest/buildkite-agent-darwin-arm64.sha256
https://download.buildkite.com/agent/stable/3.73.1/buildkite-agent-darwin-arm64.sha256

(Note we don't produce darwin-386 binaries anymore, that were shown in #500)

@DrJosh9000 DrJosh9000 mentioned this issue Jul 18, 2024
2 tasks
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

No branches or pull requests

2 participants