This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-29
Channels
- # announcements (7)
- # asami (13)
- # babashka (22)
- # beginners (52)
- # calva (95)
- # clj-kondo (14)
- # cljs-dev (7)
- # clojars (5)
- # clojure (94)
- # clojure-austin (5)
- # clojure-dev (15)
- # clojure-europe (25)
- # clojure-nl (18)
- # clojure-uk (15)
- # clojuredesign-podcast (28)
- # clojurescript (63)
- # copenhagen-clojurians (1)
- # cursive (3)
- # datalevin (7)
- # datascript (13)
- # datomic (13)
- # duct (14)
- # emacs (24)
- # events (1)
- # fulcro (13)
- # graphql (7)
- # kaocha (4)
- # lambdaisland (6)
- # lsp (22)
- # music (5)
- # off-topic (24)
- # rdf (1)
- # re-frame (3)
- # reitit (9)
- # shadow-cljs (23)
- # sql (15)
- # testing (4)
- # tools-build (6)
- # vim (7)
- # vscode (7)
- # xtdb (21)
Hi, I’m not sure if this question belongs here, but tools-build is my best guess right now. I’m setting up clojure automated deployments using github actions, all working fine. One problem though: when I get an exception in the build, the output is saved in an EDN file on the filesystem (I get messages like
Full report at:
/var/folders/bh/094hxw3x4bx4msfv9n9jz6580000gn/T/clojure-10505501116317827051.edn
at the end of the failed build).
The problem I have is that this file is not available to me when the build is run via github actions - I have no easy way to view it. Is there a way to configure the clojure deps build process to print this info to stdout/stderr?
Thanks in advance.
You can do clj -J-Dclojure.main.report=stderr ...
to print the exception into stderr instead of a file.