This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-03
Channels
- # announcements (1)
- # babashka (22)
- # beginners (176)
- # calva (10)
- # cider (4)
- # circleci (5)
- # cljsrn (20)
- # clojure (28)
- # clojure-europe (11)
- # clojure-italy (5)
- # clojure-nl (5)
- # clojure-spec (1)
- # clojure-sweden (2)
- # clojure-uk (29)
- # clojuredesign-podcast (4)
- # clojurescript (38)
- # code-reviews (25)
- # conjure (1)
- # core-typed (1)
- # data-science (16)
- # datomic (23)
- # figwheel-main (16)
- # fulcro (48)
- # helix (9)
- # jobs (3)
- # juxt (5)
- # kaocha (17)
- # malli (19)
- # mount (9)
- # nrepl (4)
- # off-topic (35)
- # pathom (7)
- # re-frame (28)
- # reagent (26)
- # reitit (1)
- # releases (1)
- # remote-jobs (5)
- # sci (6)
- # shadow-cljs (36)
- # spacemacs (3)
- # sql (8)
- # tools-deps (13)
- # unrepl (1)
- # vim (4)
- # xtdb (8)
@seancorfield I am assuming the following command just downloads project dependencies and prints out the classpath to avoid doing anything else, similar to doing lein deps
without running anything else.
clojure -R:test:runner -Spath
Full context, its used in a CircleCI step in https://github.com/seancorfield/next-jdbc/blob/develop/.circleci/config.yml#L13
Just checking if I understood this correctly. Thanks.Yes @jr0cket -- Using -R
instead of -A
means that just the "resource" portion of those aliases is used (in particular :main-opts
is ignored) and -Spath
is basically a throwaway to avoid clojure
running any code or starting a REPL. -e nil
is another possibility (that wouldn't print anything -- but I find either -Spath
or -Stree
can be a useful debugging aid to double-check dependencies are correct).
Thanks for confirming, yes that all makes sense. I like the idea of having more debugging info. I have a nice simple config.yml file working, which uses an image with the latest release of Clojjure CLI tools and OpenJDK 11. https://github.com/practicalli/random-clojure-function/blob/live/.circleci/config.yml I'll build on that config and add more features as needed. Probably the next thing is to deploy apps to Heroku on successful build of live branch. CircleCI is really simple to use compared to the corporate configuration of TeamCity I spent several weeks configuring in a bank :)
I find GitHub Actions even simpler (but less sophisticated). Several of my projects have both.
With GHA it is trivial to have matrix testing over a variety of JDK versions. With CircleCI it is possible but a lot more work.