xpg
Experiences parsing compiler and dialyzer errors and warnings in build system
What are people’s experiences in parsing compiler and dialyzer errors and warnings within their build systems?
I’m using Jenkins myself, and used to use the (now deprecated) Warnings Plugin. I had a small Groovy script setup to collect errors and warnings, but I never got it working perfectly.
Now I’m replacing the deprecated Jenkins plugin with a new one. So now I’m trying to figure out what the best way is to get both errors and warnings from both the Elixir compiler and Dialyzer into Jenkins.
There are many ways to attack this problem, and I guess it’s not unique to Jenkins either. Unfortunately, my Google Search skills have failed me, so I haven’t been able to find anything usable.
What do you guys do?
Most Liked
hauleth
In theory - yes. In practice it would be much harder, especially as it will not be able to catch all messages anyway due to fact that Elixir compile time is in fact runtime, so you can always use IO.puts/1 to output additional messages.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









