Robotics · CI & build health

ros2-ci-bridge

An offline analysis layer that turns ROS2 build and test logs into an evidence-graded health report, with a clean scenario proving it does not manufacture alarms.

Public · synthetic demo
The problem

Build logs are evidence, but only if the same input yields the same report.

The bridge parses package, build, test, and flaky-test signals without claiming more than the logs establish.

The money shot

The same analyzer distinguishes green from broken

Side-by-side scenarios
measuregreenbroken
packages discovered33
built successfully32
failed packages01 — sensor_fusion_utils
tests1910
test errors01
candidate flaky tests01
findings emitted818

On green logs, the hedge sections stay almost empty. Quiet input produces a quiet diagnosis instead of alert noise.

Reproducibility signal
green  report md5: c3280360178073695b7344077e88615c
broken report md5: a6b1207b4120a6191fac13c42c63a280

Identical input produces the identical report digest.

Honest limitations

This layer analyzes supplied build and test logs. It does not claim the robot works, is safe, or is reproducible beyond the evidence recorded by those logs.

This page reports the supplied sample output and its stated limits. Inspect the code and evidence ↗