babashka-sci-dev

Adam Kalisz 2022-09-27T16:24:19.249369Z

I was wondering, where can I add the shasums generation? Related to this issue: https://github.com/babashka/babashka/issues/1369

Adam Kalisz 2022-09-27T16:24:59.763139Z

It should be a one or two simple tasks in the build.

borkdude 2022-09-27T20:27:35.961669Z

@adam.kalisz Welcome! I think @lee or @rahul080327 mentioned recently that the graal native image already produces SHA files, but I'm not 100% sure who said this. But I think we need to produce sha256 files of the tar.gz right, or the binary?

borkdude 2022-09-27T20:30:22.277939Z

So each CI build uploads the binary to Github releases. This script for this is in babashka.release-artifact

borkdude 2022-09-27T20:30:48.723989Z

Instead of just uploading the artifact, we could also upload an additional SHA256 file and that's it I think :)

lread 2022-09-27T20:31:00.459319Z

Ya dat was me.

lread 2022-09-27T20:36:07.643429Z

I was only noticing that they included sha256 files https://github.com/graalvm/graalvm-ce-builds/releases/. For your bad curl downloads problem. On that note, is wget any better than curl at being noisy when things go wrong? I think it has some retry logic… maybe…

borkdude 2022-09-27T20:37:29.085669Z

ah yes, espresso-installable-svm-java11-darwin-aarch64-22.2.0.jar.sha256 - I think we should also produce such files and upload them along the other files that are part of the release