This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-10
Channels
- # aleph (4)
- # aws (2)
- # bangalore-clj (2)
- # beginners (84)
- # boot (25)
- # cider (3)
- # cljsrn (3)
- # clojure (57)
- # clojure-italy (5)
- # clojure-losangeles (3)
- # clojure-russia (7)
- # clojure-spec (18)
- # clojure-uk (29)
- # clojurescript (90)
- # cursive (11)
- # data-science (68)
- # datascript (2)
- # datomic (25)
- # duct (3)
- # fulcro (13)
- # graphql (7)
- # immutant (1)
- # jobs (1)
- # leiningen (12)
- # lumo (1)
- # off-topic (51)
- # om (43)
- # onyx (15)
- # parinfer (10)
- # pedestal (4)
- # re-frame (7)
- # reagent (42)
- # ring-swagger (42)
- # rum (1)
- # shadow-cljs (172)
- # spacemacs (10)
- # specter (4)
- # sql (4)
- # test-check (19)
- # unrepl (54)
- # yada (3)
we think that
with lein 2.8.0 the exit codes are not being respected if installed via package manager
and so https://semaphoreci.com/docs/failed-build-reported-as-passed.htmlI thought there was an update after the initial 2.8 that fixed that
How to get a command output into my code/env?
on :cljsbuild
, I'm using foo.core/version ~(-> (clojure.java.shell/sh "git" "rev-parse" "HEAD") :out clojure.string/split-lines first)
in :closure-defines
. But not sure how to do it in "jvm" clojure.
@lepistane 2.8.1 was released to address that particular issue 🙂