Fork me on GitHub
#circleci
<
2021-10-26
>
slipset09:10:51

Hey, any chance https://github.com/circleci/analytics-clj/pull/17 could get some love/attention 🙂

lread15:10:14

I’ve been out of the loop on changes to CircleCI Clojure images. What I’ve been using is now considered “legacy” https://github.com/CircleCI-Public/circleci-dockerfiles and no longer updated. It seems “next-generation convenience images” are the new cat’s pyjamas. The newer convenience images do include a JDK base image but nothing Clojure specific. I’m wondering if there is a default best practice for Clojure images/setup on CircleCI these days.

slipset15:10:55

I had to update an image today, so I went here https://circleci.com/docs/2.0/docker-image-tags.json

lread15:10:46

Thanks @slipset, if I understand correctly, those are now considered “legacy” images. But I might not understand correctly.

slipset16:10:06

openjdk11/lein-2.9.7 was current enough for me this morning 🙂

lread17:10:33

Sure, makes sense! Just wondering what advice is from CircleCI moving forward.

lread17:10:51

Maybe @marc-omorain has some guidance for us?

Marc O'Morain19:10:27

You can bring/use any Docker image. The docker images in the “circleci” namespace are no longer going to be updated - the ones in the “cimg” namespace will be.

đź‘Ť 1
Lennart Buit21:10:54

maybe this is an “us” problem, but is something happening with circleci? I get custom_performance-plan-executor-unavailable errors, whereas builds would run just fine 20 minutes ago

âž• 1
Lennart Buit21:10:22

(just wanna know if its a problem on our end, if it doesn’t ring a bell, it must be us 🙂 )

thumbnail21:10:45

This has fixed itself 🤷:skin-tone-2:

Marc O'Morain09:10:06

This was a bad deploy that we rolled back. Sorry for the inconvience.

1
Lennart Buit09:10:49

Oh that happens ^^.

1