This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-18
Channels
- # ai (6)
- # announcements (3)
- # babashka (5)
- # beginners (22)
- # calva (1)
- # cider (3)
- # clj-kondo (30)
- # clj-yaml (20)
- # clojure-europe (83)
- # clojure-spec (4)
- # clojurescript (6)
- # fulcro (1)
- # graalvm (16)
- # holy-lambda (5)
- # malli (33)
- # music (1)
- # nbb (14)
- # releases (3)
- # sci (13)
- # scittle (3)
- # shadow-cljs (35)
- # xtdb (7)
- # yada (2)
I'm giving a try on Oracle Cloud free tier, which allows you have a instance and configure github self runner for that, then we may have aarch64 builds entirely on github actions
I applied clojure-lsp for https://www.macstadium.com/opensource-application, not sure if they will accept, but worth the try :)
You already are using CirrusCI, but they don't support Github self-hosted hooks right?
yeah, I'm having some race conditions issues where cirrus builds before github action and publish to a wrong clojure-lsp dev release, I could try trigger the cirrus CI build via API in the future
I have solved this problem by using my own library which uploads to Github releases in an idempotent way
but maybe the problem is that you're using a very fine-grained version number with milliseconds in it
yep, not milliseconds, but https://github.com/clojure-lsp/clojure-lsp/blob/master/scripts/clojure_lsp/release_artifact.clj#L25 is the issue, we expect the release dev tag was already built