This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-20
Channels
- # announcements (5)
- # asami (7)
- # babashka-sci-dev (36)
- # beginners (50)
- # calva (47)
- # cider (1)
- # clj-kondo (19)
- # clojure (33)
- # clojure-europe (25)
- # clojure-nl (2)
- # clojure-uk (4)
- # clojurescript (26)
- # conjure (2)
- # cursive (5)
- # datalog (6)
- # fulcro (5)
- # graalvm (12)
- # leiningen (1)
- # malli (30)
- # off-topic (5)
- # rdf (4)
- # ring (11)
- # shadow-cljs (55)
@rahul080327 > the runners take a bit of time to provision what's that?
So we are using the same infra but shorting the steps, so it could take a while for example the mac one to be provisioned. Then it shorts. So whole run could last upto few minutes
This is to keep the structure same as the required checks in GitHub
We can think of a way to have smaller runner configs for shorted pipelines in a follow up pr
Yep. It's all pulled into its own fn, should be easy to implement
@rahul080327 docker step is failing now
Right, will take a look as soon as I'm back home
This wasn't running in the Pr 😕
running https://github.com/babashka/babashka/pull/1300 with docker enabled
well not much use without changing the docker script too when not on master, but should fix it. the name of the artifact was wrong, checked it now on the PR that its fixed
its interesting that the release and setup musl scripts have different default values for BABASHKA_ARCH
env var
things i learn about the codebase everyday
correct artifacts: https://app.circleci.com/pipelines/github/babashka/babashka/5864/workflows/18385bf3-7728-42d5-980d-bd5525f42de9
this can be merged if youre okay with it, otherwise i can modify the docker script to run on non master to test too
@rahul080327 can you check on dockerhub if everything looks ok over there too ?
well nothing was pushed there, the last run failed before pushing anything, this one was skipped
i have to change the docker script a bit to make it do things on a branch
issue was that the artifacts were named _x86_64_
and the docker script wants _amd64_
I wonder why this was an issue since the dynamic config should be equal to the previous config when there are things to build, right?
the last commit has a [skip ci] 😕
> I wonder why this was an issue i missed the fact that babashka_arch env var is only needed for aarch64, others use the default values and the default values are different for the release and musl scripts
manually triggering pipeline from circle