Fork me on GitHub
#cljdoc
<
2018-12-15
>
bbrinck03:12:52

I’m trying to republish docs for a SNAPSHOT build. I’ve clicked the hidden “rebuild” button, but from looking at the logs for circleci job, it looks like it’s still downloading an older version of the snapshot jar

bbrinck03:12:50

Is using the “rebuild” for snapshot the best way to check my doc changes? I’d like to confirm the docs look good before my next release to avoid needing to do another release just to fix docs

bbrinck03:12:22

For context, I’ve published expound-0.7.2-20181215.030535-8.jar to clojars, but this job (https://circleci.com/gh/martinklepsch/cljdoc-builder/8355) seems to indicate cljdoc is downloading expound-0.7.2-20181210.031342-7.jar

bbrinck03:12:42

I may be misunderstanding how SNAPSHOT builds work

martinklepsch08:12:35

Sometimes it takes a while for a new snapshot to be picked up. I’m not entirely sure why this is but I guess it’s either the Clojars CDN or CircleCI already having the previous SNAPSHOT in a cache somewhere (SNAPSHOTS are usually refreshed once in 24hrs)

martinklepsch08:12:56

For now the recommended way to verify your changes will look as expected is to run cljdoc locally: https://github.com/cljdoc/cljdoc/blob/master/doc/running-cljdoc-locally.md

martinklepsch08:12:15

This is a bit more involved and there is an issue about making this easier but it’ll take time to get there

danielcompton04:12:58

It'll be the CircleCI Maven cache that is caching snapshot checking

bbrinck00:12:56

I can’t run it locally right now since my hard drive suddenly died late last night. I will try a rebuild via website when I get home - enough time has passed that the newer snapshot may be available on circle. Thanks for your help!

Avichal21:12:45

Hello, I have added an ADR for the caching system that stores data from multiple data sources to make it available for rendering docs: https://github.com/cljdoc/cljdoc/pull/239/commits/94d42d8962fb1367786ba44ff0f645d3f293e0ae Please feel free to share your thoughts 🙂

parrot 4
❤️ 4