Currently, it appears that the clang-tidy task invokes one command to scan the entire codebase sequentially, and thus takes multiple hours to complete. To get better use out of clang-tidy and encourage its use in a popular builder, we should change it to run individually on each source file, in a parallel fashion.
- is related to
-
SERVER-27984 Add clang-tidy run in addition to lint
- Closed
-
SERVER-49800 add use-after-move rule to clang-tidy evergreen builder
- Closed
- related to
-
SERVER-51240 Add clang tidy rules to prevent const return by value and (in declarations) const pass by value
- Closed
-
SERVER-54210 add clang-tidy to commit queue tasks
- Closed