What
Integrate the S-CORE standard static analysis CI workflow into the inc_time
pipeline. The workflow runs bazel build --config=lint //score/... to execute
Clang-Tidy via Bazel aspects and collect reports as CI artifacts.
Steps:
- Add a
build:lint config to .bazelrc using the Clang-Tidy aspect from
score_cpp_policies (depends on Task 1)
- Create
.github/workflows/static_analysis.yml:
name: Static Code Analysis
on:
pull_request:
types: [opened, reopened, synchronize]
push:
branches: [main]
merge_group:
types: [checks_requested]
jobs:
static-analysis:
uses: eclipse-score/cicd-workflows/.github/workflows/static-analysis.yml@main
with:
bazel-targets: "//score/..."
bazel-config: "lint"
References
Reusable workflow:
- https://github.com/eclipse-score/cicd-workflows/blob/main/.github/workflows/static-analysis.yml
- Current .bazelrc (no lint config yet):
https://github.com/eclipse-score/inc_time/blob/main/.bazelrc
- S-CORE process (Static Code Analysis section):
https://github.com/eclipse-score/score/blob/main/docs/contribute/development/cpp/code_analysis.rst
Estimates for realization
S - Day
Category
Requirements / Architecture
What
Integrate the S-CORE standard static analysis CI workflow into the inc_time
pipeline. The workflow runs
bazel build --config=lint //score/...to executeClang-Tidy via Bazel aspects and collect reports as CI artifacts.
Steps:
build:lintconfig to.bazelrcusing the Clang-Tidy aspect fromscore_cpp_policies(depends on Task 1).github/workflows/static_analysis.yml:References
Reusable workflow:
https://github.com/eclipse-score/inc_time/blob/main/.bazelrc
https://github.com/eclipse-score/score/blob/main/docs/contribute/development/cpp/code_analysis.rst
Estimates for realization
S - Day
Category
Requirements / Architecture