This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-13
Channels
- # aleph (8)
- # announcements (3)
- # beginners (36)
- # calva (1)
- # cider (1)
- # circleci (3)
- # clj-kondo (9)
- # cljdoc (58)
- # clojars (7)
- # clojure (70)
- # clojure-europe (13)
- # clojure-japan (1)
- # clojure-nl (8)
- # clojure-russia (2)
- # clojure-uk (7)
- # clojuredesign-podcast (4)
- # clojurescript (67)
- # clojureverse-ops (14)
- # cursive (6)
- # data-science (1)
- # datahike (3)
- # datomic (6)
- # docker (1)
- # events (2)
- # figwheel-main (9)
- # fulcro (4)
- # graalvm (33)
- # graphql (8)
- # helix (1)
- # jobs (1)
- # leiningen (3)
- # lsp (39)
- # malli (9)
- # minecraft (31)
- # nextjournal (7)
- # off-topic (6)
- # portal (22)
- # re-frame (5)
- # reitit (5)
- # remote-jobs (1)
- # shadow-cljs (55)
- # sql (22)
- # tools-build (3)
- # tools-deps (4)
- # xtdb (6)
Does anyone have any ideas why I’m getting build failures for releases like this: https://cljdoc.org/builds/49563
Am I doing something wrong?
@rickmoynihan, the double v on the version looks very suspicious:
@lee: that was on a later build. i.e. I added it because I thought the lack of a v
in the git tag might be causing it
but I got the same error with or without.
the build I pasted above is for the preceding one 0.1.4
One difference is that the jars here have been built and deployed with the new tools.build stack
does the process assume a git tag is created? Because the tools.build deploys don’t seem to tag or push tags — I created them manually later, but I think before triggering a build in cljdoc
There is something confused about the version tag… cljdoc did find your README so it is successfully reaching back to your repo… (It finds your repo via scm info in the from the deployed pom on clojars)…
ahh so it expects pom.xml
in the repo to be correct? Rather than just a template for tools.build
Analysis seems to be https://github.com/Swirrl/dogstatsd/blob/adff85c7b36b00e3c34f3e04608eefeaa21ae9e8/src/swirrl/dogstatsd/specs.clj#L20
ah ok I just fixed that locally
repl out of sync
thanks
My pleasure. I found the issue by looking at https://app.circleci.com/pipelines/github/cljdoc/builder/24151/workflows/14b032c0-78dc-4f02-9a28-989ec83cba43/jobs/40526?invite=true#step-104-239.
I really need to add some tests to this project; to help catch this sort of thing, unfortunately the project I forked it from had none
Yeah that would probably help. In the meantime, if you want, you can also https://github.com/cljdoc/cljdoc/blob/master/doc/running-cljdoc-locally.adoc#verifying-docs-prior-to-publish-to-clojars.
I’m still getting a similar error https://cljdoc.org/builds/49570 - but can’t seem to find the job on circle
@lee hmm still having problems :thinking_face:
Ah snapshot builds. Haven’t tried those yet myself with cljdoc. But… the build log is simply telling you that tag v0.1.7-SNAPSHOT
does not exist in your repo.
I seem to recall it working much better in the past with leiningen projects — Does tools.build
do less of things that you rely on?
I’ve tried tools.build on a couple of projects and found it worked fine for me. I’m not a lein guy though. But I expect tools.build gives you more control and therefore you have to be more explicit.
can you rerun a build?
So leiningen probably fills the pom scm tag with the git sha. Which might be more appropriate for a snapshot build?
yeah — is the pom taken from clojars or the git repo?
I’m assuming the jar
@lee: hmm still getting the issue — this time I’ve changed the build process to create the version and tag, and push them before deploying to clojars. So the tag exists but I get this error: https://cljdoc.org/builds/49576
I don’t prefix the tags with v
but when I did that earlier it ended up looking for tags prefixed with vv
@rickmoynihan this must be driving you slightly barmy!
😆 only slightly
I probably shouldn’t have started shaving this yak… They’re always hairier than you expect! 😆
I successfully deployed and built docs for rewrite-clj recently… lets compare with that.
I will need to finish for the day in a few minutes btw
Ok the url in my docs on rewrite-clj contains no v prefix for the version: https://cljdoc.org/d/rewrite-clj/rewrite-clj/1.0.699-alpha/doc/readme
My git repo tags do include the v prefix https://github.com/clj-commons/rewrite-clj/tags
And my scm tag is formulated to match the my git repo tag https://github.com/clj-commons/rewrite-clj/blob/6d1ebb0dbed7fb1a1e1109e1957d6f3996e190dd/build.clj#L48
ahh I think that’s what’s different — my tag and scm tag don’t quite match
I’m using sean corfields tools build wrapper (mainly because it came with the project template)
and I think it sets this for you
Yeah — I was planning on going that way too — but just ran with what the template gave me
it came from deps-new
Thanks for your help! 🙇
Per the build-clj
README:
• jar
• Requires: :lib
and :version
,
• :target
, :class-dir
, :basis
, :resource-dirs
, :scm
, :src-dirs
, `:tag` (defaults to (str "v" version)
), :jar-file
,
(my emphasis)