This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-21
Channels
- # announcements (3)
- # babashka (26)
- # beginners (45)
- # calva (10)
- # chlorine-clover (9)
- # cider (4)
- # clj-kondo (7)
- # cljs-dev (10)
- # clojure (95)
- # clojure-europe (33)
- # clojure-france (5)
- # clojure-nl (3)
- # clojure-spec (2)
- # clojure-sweden (3)
- # clojure-uk (33)
- # clojurescript (54)
- # conjure (101)
- # core-async (14)
- # cursive (1)
- # data-science (91)
- # datascript (3)
- # datomic (16)
- # figwheel (3)
- # figwheel-main (15)
- # fulcro (35)
- # ghostwheel (5)
- # graalvm (13)
- # helix (29)
- # java (5)
- # jobs (6)
- # kaocha (6)
- # leiningen (1)
- # meander (12)
- # off-topic (54)
- # pathom (13)
- # re-frame (16)
- # reagent (8)
- # reitit (4)
- # rum (3)
- # shadow-cljs (49)
- # spacemacs (2)
- # sql (5)
- # tools-deps (10)
- # xtdb (8)
- # yada (3)
For native-image based tools, how do people automate their github releases? (cross compiling, creating release, uploading artifacts...)
@plexus Cross compiling isn't a thing in GraalVM. You can check out my GraalVM projects for ideas. I have a bunch of them.
fwiw I still create releases manually and upload the artifacts manually, because I also want to post release notes simultaneously.
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.
For Windows I use AppVeyor although I could use Github actions as well - it's just that Appveyor was first.
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
@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
there is an action to provision GraalVM for GH actions - https://github.com/marketplace/actions/setup-graalvm-environment
:thumbsup: