Hi all, again! I'm investigating slow Bazel builds on our CI, tracing suggests that rules_detekt consumes about 25 seconds (!) during Bazel query we don't even have any rules_detektbuild action in the build graph nor build graph at all — justbazel query`.
It seems like it happens because rules_detekt dependencies that we pull via rules_jvm_external are not pinned so that users could override versions I guess, but without pinning we never cache them properly.
We should be able to come up either with a fix in rules_detekt or an instruction on workarounding this similar to https://blog.aspect.dev/avoid-eager-fetches
Hi all, again! I'm investigating slow Bazel builds on our CI, tracing suggests that
rules_detektconsumes about25 seconds(!) during Bazelquery we don't even have anyrules_detektbuild action in the build graph nor build graph at all — justbazel query`.It seems like it happens because
rules_detektdependencies that we pull viarules_jvm_externalare not pinned so that users could override versions I guess, but without pinning we never cache them properly.We should be able to come up either with a fix in
rules_detektor an instruction on workarounding this similar to https://blog.aspect.dev/avoid-eager-fetches