[GH-ISSUE #2483] Move clang-tidy and cppcheck to a separate CI stage #1218

New issue

Open

opened 2026-03-04 01:52:17 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:52:17 +03:00

Owner

Originally created by @gaul on GitHub (Jul 1, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2483

Instead of running clang-tidy and cppcheck across all CI targets, we could put these only in a separate CI target. Running across all targets exposes us to bugs in older versions, e.g., #2477, #2163, #1869, and wastes CI run-time doing duplicate work. Doing this would be similar to the existing valgrind target which only runs on ubuntu-latest.

Originally created by @gaul on GitHub (Jul 1, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2483 Instead of running clang-tidy and cppcheck across all CI targets, we could put these only in a separate CI target. Running across all targets exposes us to bugs in older versions, e.g., #2477, #2163, #1869, and wastes CI run-time doing duplicate work. Doing this would be similar to the existing valgrind target which only runs on ubuntu-latest.

kerem commented

2026-03-04 01:52:18 +03:00

Author

Owner

@gaul commented on GitHub (Jul 1, 2024):

Also shellcheck.

@gaul commented on GitHub (Jul 1, 2024): Also shellcheck.

kerem commented

2026-03-04 01:52:18 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 1, 2024):

It seems best to set up separate CIs for each.
It seems best to base them on an OS (distribution) that can support the latest version as quickly as possible.(especially cppcheck)

@ggtakec commented on GitHub (Jul 1, 2024): It seems best to set up separate CIs for each. It seems best to base them on an OS (distribution) that can support the latest version as quickly as possible.(especially cppcheck)