Update readme - #4
Closed
BjoernAtBosch wants to merge 50 commits into
Closed
Conversation
…ency Remove proprietary CRC dependency and disable SubTLV features
Signed-off-by: Björn Hornburg <[email protected]>
Co-authored-by: Timofte Bogdan <[email protected]>
This reverts commit 3d7604b.
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
Contributor
Author
|
Sorry - wrong repo |
lavrovvalera
added a commit
to lavrovvalera/inc_time
that referenced
this pull request
Aug 3, 2026
Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4
lavrovvalera
added a commit
to lavrovvalera/inc_time
that referenced
this pull request
Aug 11, 2026
Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4
lavrovvalera
added a commit
to lavrovvalera/inc_time
that referenced
this pull request
Aug 11, 2026
Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4
umaucher
pushed a commit
that referenced
this pull request
Aug 11, 2026
* Update README.md (#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap #4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 14, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 14, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 14, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 14, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 17, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 17, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 17, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 18, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 18, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
ryan-steel
pushed a commit
to etas-contrib/score_time
that referenced
this pull request
Aug 18, 2026
* Update README.md (eclipse-score#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap eclipse-score#4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]>
Copilot AI
pushed a commit
that referenced
this pull request
Aug 26, 2026
* Update README.md (#152) * ci(codeql): production-only build via cquery; Replace SARIF post-processing with build-level test exclusion: - Use bazel cquery --config=codeql with 'except attr(testonly, 1, ...)' to resolve production-only labels before the traced build; testonly targets, platform-incompatible targets (e.g. QNX-only), and multi-config duplicates are all excluded before any source file enters the database - Add --skip_incompatible_explicit_targets to bazel build so explicit label lists tolerate platform-incompatible targets gracefully Fix BUILD hygiene: - Add testonly=True to svt_receiver_mock alias (//score/time_daemon/src/ipc) - Add testonly=True to HighResSteadyTimeBenchmark cc_binary Add RULE-7-0-4 deviation (tool defect: stream operator<< mis-flagged as shift) Refactor tooling layout (module-agnostic vs module-specific split): - Extract codeql.bzl macro; BUILD reduced to a 3-line load + call - Move coding-standards.yaml to tools/static_analysis/ (process_coding_standards_config scans recursively, root location is not required) - coding-standards.yaml declared as explicit Bazel filegroup for incremental rebuild tracking Update README: file layout section, cquery-based phase descriptions, build-level test exclusion explanation, remove stale gap #4 * ci(codeql): run codeql on ci Replace the shared eclipse-score/cicd-workflows CodeQL wrapper with a direct invocation of tools/static_analysis:codeql_lint, mirroring the local workflow exactly. Motivation: - The shared wrapper used github/codeql-action/init (unpinned CodeQL version) and packs: codeql/misra-cpp-coding-standards (downloaded from registry at runtime, no deviation processing). - Our codeql_lint uses the pinned CLI (@codeql_bundle v2.21.4), the pinned MISRA pack (@codeql_coding_standards_compiled v2.61.0), and runs process_coding_standards_config to apply coding-standards.yaml deviations before the analysis. Findings from known tool defects (e.g. RULE-7-0-4) are suppressed in the results. Changes: - Replace reusable workflow call with a standalone job - Add more-disk-space (level 4) — CodeQL database + tooling requires headroom - Run bazel run //tools/static_analysis:codeql_lint with the same arguments as the local invocation; output goes to runner.temp - Upload codeql-time.sarif to GitHub Security tab via upload-sarif@v3 - Upload analysis_reports/ as a build artifact for audit/compliance use Co-authored-by: Ryan Steel <[email protected]> Co-authored-by: NEOatNHNG <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.