Fork me on GitHub
#graalvm
<
2020-05-21
>
plexus14:05:32

For native-image based tools, how do people automate their github releases? (cross compiling, creating release, uploading artifacts...)

borkdude15:05:55

@plexus Cross compiling isn't a thing in GraalVM. You can check out my GraalVM projects for ideas. I have a bunch of them.

borkdude15:05:08

fwiw I still create releases manually and upload the artifacts manually, because I also want to post release notes simultaneously.

ghadi15:05:01

GitHub actions are pretty nice. support mac and windows, too IIRC

ghadi15:05:22

Might not have enough RAM for Graal NI, dunno

borkdude15:05:19

I build babashka on Github actions as well as CircleCI. The latter provider had to bump my memory privileges while I can still build on the normal plan with GH.

borkdude15:05:21

For Windows I use AppVeyor although I could use Github actions as well - it's just that Appveyor was first.

plexus16:05:12

Thanks for the input. I like to automate these things as much as possible, fine if it's scripts that I run locally, but might look into gh actions

uochan22:05:49

@plexus Dad is using github actions to automate building native-images and releaseing:slightly_smiling_face: Pushing a new tag is the trigger. https://github.com/liquidz/dad/blob/master/.github/workflows/native_image.yml

delaguardo08:05:26

there is an action to provision GraalVM for GH actions - https://github.com/marketplace/actions/setup-graalvm-environment

uochan08:05:15

Thanks! I know your github actions, and I have a plan to use them 👍

borkdude22:05:02

@liquidz.uo thanks for sharing, I might borrow that idea one day

👍 4