diff --git a/defs.bzl b/defs.bzl index b361b13c..387f0994 100644 --- a/defs.bzl +++ b/defs.bzl @@ -50,6 +50,12 @@ load( _platforms_transition = "platforms_transition", ) +# Store rule, for uploading results to a CodeChecker server +load( + "//src:store.bzl", + _store = "store", +) + codechecker_test = _codechecker_test codechecker_suite = _codechecker_suite codechecker_config = _codechecker_config @@ -57,6 +63,7 @@ codechecker_toolchain = _codechecker_toolchain compile_commands = _compile_commands clang_tidy_test = _clang_tidy_test clang_analyze_test = _clang_analyze_test +codechecker_store = _store # Helper for the platform suffix codechecker_suite() adds to its test names get_platform_alias = _get_platform_alias diff --git a/docs/codechecker.md b/docs/codechecker.md index 7f4edaa4..57b8c566 100644 --- a/docs/codechecker.md +++ b/docs/codechecker.md @@ -78,17 +78,18 @@ bazel test ... ### Analysis results You can find the analysis results in the `bazel-bin/` folder, on which you -can run [`CodeChecker store`](https://github.com/Ericsson/codechecker/blob/master/docs/web/user_guide.md#store) -or [`CodeChecker parse`](https://github.com/Ericsson/codechecker/blob/master/docs/analyzer/user_guide.md#parse). +can run [`CodeChecker parse`](https://github.com/Ericsson/codechecker/blob/master/docs/analyzer/user_guide.md#parse). The precise output path to the directory can vary, but you should look for `your_codechecker_rule_name/codechecker-files/data`. -In simpler cases, something like the following: ```bash CodeChecker parse bazel-bin/your_codechecker_rule_name/codechecker-files/data -CodeChecker store bazel-bin/your_codechecker_rule_name/codechecker-files/data -n "Run name" ``` +To upload results to a CodeChecker server, use the [`codechecker_store()`](store#store) +rule instead of calling `CodeChecker store` manually. See [Store](store) for +details. +