Fork me on GitHub
#babashka-sci-dev
<
2022-04-13
>
cap10morgan15:04:58

Seems like GraalVM is going to have macOS arm64 support (in a stable release) before CircleCI does (https://circleci.canny.io/cloud-feature-requests/p/support-new-m1-arm-based-macs), huh?

borkdude15:04:36

Guess so. We can take whatever free CI comes first with M1 support. Maybe even Oracle cloud? ;)

👍 1
cap10morgan16:04:14

Not sure if this would be a viable option or not, but a few day-jobs ago we used an interesting CI service called BuildKite where they hosted the web UI but you hosted the runners. I guess GitHub Actions supports the same model now, so that's probably the more straightforward approach. Want to run a Patreon campaign for a Mac Studio build machine on your desk, @borkdude? 😉

lispyclouds16:04:54

Yeah actions had self hosted runners since a while now, build-machine-on-desk is indeed a nice one

lispyclouds16:04:42

we have been using self hosted ones for a lot of (mis)usecases

cap10morgan16:04:22

I setup a "spin up on demand, spin down when quiet" self-hosted GHA runner thing in AWS awhile back just b/c we needed more resources than their runners gave us. I wonder what the cost of doing that w/ AWS's M1 Mac instances would be? Probably could run that for awhile before it hit Mac Studio cost. 🙂

cap10morgan16:04:22

hopefully it will be all moot soon. somebody's got to come out with support in a free hosted CI thing before too long, right? (right?!) 😆

lispyclouds16:04:07

or the rate at which graal people are running, cross compiling support from them

lispyclouds16:04:58

that being a JVM thing and being platform specific is a bit weird for me honestly 😛

lispyclouds16:04:43

anyways since a bunch of us have M1 machines now, we can test and ship binaries til we get CI, releases are anyways manual for now

cap10morgan16:04:18

yeah, I'm happy to contribute builds if needed

cap10morgan16:04:23

guaranteed 98% backdoor-free! 😉