Clojurians Log v2

I'm fixing CI issues in my bb branch. But now the only failing CI job is the bb tests bwahaha. I'll fix those later today

done ✅

and merged, thank you!

Those tickets are mostly fixed?

They are "merged" and the issue is "closed", but no new cloverage version was released since 1.2.4. Looks like cloverage's CI is broken for more than 1y+

This thread had quite a bit of discussion around issues with Cloverage and possible alternative approaches: https://clojurians.slack.com/archives/C03S1KBA2/p1764412928038799 (disclaimer: I've never managed to get Cloverage working with our codebase, at work, and I'm not particularly enthusiastic about test coverage metrics in the first place).

Thanks, I managed to find another thread of yours where you talked about Clofidence. I didn't look deeper after seeing it doesn't support cobertura or jacoco output formats. > and I'm not particularly enthusiastic about test coverage metrics in the first place Do you use a different tool to measure a PR?

"measure" a PR? No, I don't do that.

I find coverage reports useful when I adopt a project from someone else. Not at all as a goal to reach some percentage of coverage, but just to learn what code the current tests cover.

I recently put a lot of effort into making bb + cloverage work together and filed a PR (the bb fixes were already released)

maybe cloverage is something clj-commons could take over if the current maintainers are not interested anymore? is @lvh still involved?

I'd be open to porting it to clj-commons though it's less obvious to me that that'll fix things 🙂

I should have all of the relevant access; the real problem is just someone taking the time to actually get it fully urnning again

only if the current maintainers don't have time for it anymore, I'd say

> the real problem is just someone taking the time to actually get it fully urnning again what are the current problems?

I see that circleci isn't running anymore, but this is purely a "re-add the project" problem, it doesn't have the git credentials anymore somehow

if someone would pass it over to clj-commons I can spend a few hours on this to get it running again

maybe migrate to Github actions, since circleci seems to be causing issues lately

Yeah, we migurated it to GHA before, then a few circleci folks did work to bring circleci back, but as always the hard part there is maintenance 🙂

(FWIW I spent some time yesterday reviewing your PR, so it's not "nothing", and I think automated releases mostly worked? so yes there is no formal release but there are plenty of snapshots people can use, which seems equivalent to using gitdeps to me)

who were these people that preferred circleci? recently the last person who was at circleci from the clojure community that I knew left there. I'm still using circleci so it'd be good to have some connections... but I'm seeing more and more flakiness with it lately.

If it transfers to clj-commons, I can help with maintaining, if that’s of interest.

I think the circle people have been gone for a while, yes, and generally I think it's perfectly fine to say "sorry github actions is a way more reliable and common platform and that's what we're optimizing for"

FWIW technomancy just quit his circleci job two weeks ago or so. he was the last one in my mind. he quit because he was forced to use AI in his job which he didn't want

I'm already setting it up so CI can cut at least snapshot releases FYI

nice

one point release would be nice so I can announce it in the (today or tomorrow) bb changelogs :)

I released a new bb which can run the new cloverage

@lvh thanks! Can you maybe re-add the project to circleci? On master somehow it has trouble with the ssh git stuff. https://app.circleci.com/pipelines/github/cloverage/cloverage/106/workflows/c3c7ecbf-af4f-4e81-be0a-deb3df534d86/jobs/1890

Please make sure you have the correct access rights
and the repository exists.
error running git clone "git@github.com:cloverage/cloverage.git": exit status 128

error running git clone "git@github.com:cloverage/cloverage.git": exit status 128

how I solved this for my own project: stop following the project on circleci and then add it again

FWIW I just bit the bullet and started porting to GitHub ACtions

https://github.com/cloverage/cloverage/pull/359

only thing that doesn't work is bb -- any chance this is dependent on an unreleased feature? biggest change i could find is dev vs latest stable

ok just confiemd that's it

@lee @borkdude I have no nostalgia for the cloverage org and generally warm fuzzies for clj-commons (though I wish it was officially part of clj-together), if you're serious I'm happy to contribute; that CI PR could certainly use review

currently having claude trawl through the issue tracker for me so we can figure out what's still valid

If you're going to publish cloverage under a new group ID, you'll probably also want to rename the nses? I guess it's not as problematic for a tool as for a library but...

Please let’s publish it to the old org if possible. Easier for everyone.

Yes, if we can continue to do that, that is the best path. That has not been possible for all the projects that moved to clj-commons.

Yea, you need the bb dev build. Only that one supports .sym + .na interop on a var

But it was possible for projects if maintainers still had their Clojars credentials and made clj-commons folks part of the admin there, right? FWIW mine is borkdude

Yes, the key is access to the project group in Clojars.

My clojars user/profile/whatever-you-call-it is: lread

Yeah, agreed, if we can stay with the cloverage maven group-id on clojars that will be much nicer for users.