Wondering: is there a performance impact from running gradle builds with --stacktrace enabled by default? We are facing a gradle issue that shows up infrequently on our verification built, and in order to collect the information needed for my issue against gradle I need the corresponding stacktrace. The easiest would be to simply add --stacktrace for all our verification builds, but I am wondering if there is any "cost" associated with that?

Probably negligible

Yeah, I did a few full build runs locally with and without --stacktrace, and it's all in the same ballpark. The first time running with the parameter, it even finished 5 seconds faster than without.