This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-21
Channels
- # aws (2)
- # aws-lambda (1)
- # beginners (62)
- # cider (31)
- # cljs-dev (16)
- # cljsrn (8)
- # clojure (115)
- # clojure-greece (3)
- # clojure-israel (2)
- # clojure-italy (13)
- # clojure-nl (8)
- # clojure-russia (5)
- # clojure-spec (3)
- # clojure-uk (146)
- # clojurescript (108)
- # clojutre (5)
- # code-reviews (3)
- # cursive (48)
- # datomic (22)
- # editors (20)
- # emacs (7)
- # fulcro (16)
- # graphql (10)
- # mount (2)
- # off-topic (47)
- # onyx (22)
- # re-frame (100)
- # reagent (5)
- # reitit (7)
- # ring-swagger (6)
- # rum (5)
- # shadow-cljs (51)
- # specter (2)
- # tools-deps (95)
- # vim (10)
- # yada (7)
how does onyx manage to release everything with consistent versions? I have just 3 artifacts and it's hell already
Investment in build tooling
Everything is done through CI and scripts. Main onyx release will also update the plugins, run tests and release those too
We also have scripts in the plugins that let us release updates independent of an onyx release, so we can update those too
https://github.com/onyx-platform/onyx/blob/0.13.x/scripts/release.sh I see, thanks
You can also checkout the circle.yml to see what it does on CI after that script runs
it was a fair bit of work getting there but it paid off for us enormously over the long run.
If I started again and used a mono repo I’d probably use https://github.com/amperity/lein-monolith
I also found this which clears up much of the mystery too https://github.com/onyx-platform/onyx-release-scripts
thanks for the links, will try lein-monolith - it may be good enough for me 🙂
If I could do it again, I'd have gone with a monorepo.
I wanted separate projects in the beginning to separate issue trackers, but that never ended up being worthwhile.
It worked out fine in the end, but it was a lot more work.
deps.edn
supplants a lot of the manual work we're doing with lein-voom.
Hi, when am trying run latest dashboard with onyx 0.12.2.0 org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /onyx/<tenancy-id>/job-scheduler/scheduler code: -101 path: “/onyx/eone-cp-flow/<tenancy-id>/scheduler”
Did you switch out that tenancy ID in the error?
K. Looks like it can’t find the data in zookeeper for that tenancy
If your peers never managed to start up properly then they won’t have had a chance to write that data out