Keep PBX at v0 and simplify Jenkins quality gate
Intrepid/Prometeu/Runtime/pipeline/pr-master There was a failure building this commit

This commit is contained in:
2026-10-14 14:35:44 +01:00
parent 39468740c3
commit a2275932a5
51 changed files with 155 additions and 297 deletions
+27 -35
View File
@@ -119,22 +119,20 @@ fresh measurement.
## Commands and CI
`make ci-domains` is the authoritative repository quality gate. Both
[GitHub CI](../../.github/workflows/ci.yml) and
[Jenkins](../../files/config/Jenkinsfile) provision dependencies and invoke that
same target. `make ci` is an alias. Invoke one gate per checkout at a time.
[Jenkins](../../files/config/Jenkinsfile) orchestrates the quality gate through explicit
stages invoking Makefile targets. `make ci-domains` runs the same checks locally
and in [GitHub CI](../../.github/workflows/ci.yml); `make ci` is an alias.
Invoke one gate per checkout at a time.
The Makefile supplies this ordered sequence to the serial evidence runner:
The ordered checks are:
1. Clean LLVM coverage instrumentation from the previous run.
2. Check formatting with `cargo fmt --all -- --check`.
3. Run `cargo clippy --workspace --all-targets --all-features -- -D warnings`.
4. Test gate failure/report handling with the Python regression suite.
5. Run `cargo test --workspace --all-targets --all-features --no-fail-fast`.
6. Run the five ignored debugger socket tests through `make test-debugger-socket`.
7. Generate fresh workspace/all-feature LLVM coverage, HTML, full JSON,
Cobertura XML and summary JSON.
8. Audit source ownership/evidence and check every fixed coverage domain floor.
1. Clean previous LLVM coverage instrumentation and reports.
2. Check formatting.
3. Run workspace Clippy with warnings denied.
4. Run workspace tests across all targets and features.
5. Run the five ignored debugger socket tests.
6. Generate workspace coverage, HTML, full JSON, Cobertura and summary JSON.
7. Audit source ownership/evidence and check every fixed coverage domain floor.
The socket command is deliberately restricted:
@@ -148,8 +146,8 @@ It selects `test_debug_port_opens`, `test_debug_reconnection`,
Local sandbox TCP permissions must permit bind/connect; a permission denial is
not evidence of a debugger behavior regression.
The runner executes child Make targets with `-j1` even if the outer invocation
uses `-j`. CI invokes `make ci-domains` serially. Do not run a separate Cargo,
The local Make recipe executes child targets serially with `-j1`, even if the outer
invocation uses `-j`. Jenkins executes its stages sequentially. Do not run a separate Cargo,
coverage-clean or report process concurrently in the same checkout: serialized
steps inside one gate cannot protect against an independent process.
@@ -169,26 +167,20 @@ runner still uses this helper after installing stable Rust.
Linux packages include build-essential, pkg-config, libasound2-dev, libudev-dev,
libxkbcommon-dev, libwayland-dev, libx11-dev, libxrandr-dev, libxi-dev, Python 3,
jq, ripgrep, Git, curl and CA certificates. ALSA development files satisfy CPAL's
jq, Git, curl and CA certificates. ALSA development files satisfy CPAL's
Linux build dependency; a running audio device is not needed. Non-Linux local
hosts must already provide native compiler/SDK tools, Bash, Make, pkg-config,
Python 3, jq, rg and Git. The provisioning script verifies these commands.
Python 3, jq and Git. The provisioning script verifies these commands.
`target/quality-gate/metadata.json` records revision, dirty working tree, host,
Rust/coverage-tool versions, configuration/source fingerprints, ordered step
exit codes and report hashes. Each step has a separate combined-output log.
The runner stops on the first failed Make target and returns its nonzero exit
status; the log preserves underlying Cargo diagnostics. Three regression cases
check failure logs/identity, fresh success evidence and partial-report retention
when a later gate fails.
Jenkins owns stage status, console logs, build identity and artifact fingerprints.
GitHub retains step logs and uploaded coverage artifacts. Local execution streams
command output and stops at the first failed target; no separate Python runner
or metadata report is required.
Both pipelines discard old generated report directories before environment checks or setup and
publish current artifacts even after gate failure. An early failed gate has
metadata/logs but no old coverage report. Failure after generation preserves the
partial current reports. Prerequisite or setup failure can leave no report at all and
still fails CI. Reports are archived from `target/quality-gate/**` and
`target/llvm-cov/**`; Jenkins also publishes current HTML when present. Artifact
publication does not turn a failed gate into success.
Both pipelines discard old coverage reports before prerequisite checks or setup,
and archive current `target/llvm-cov/**` reports even after failure. Early failures
may leave no report; later failures retain partial current reports. Jenkins also
publishes HTML when present. Artifact publication does not mask a failed gate.
List domains or inspect ownership and existing evidence:
@@ -218,7 +210,7 @@ cargo test -p prometeu-cli --test automation_process packaged_installation_smoke
# File-host commit latency with the production asset decoder.
cargo test --release -p prometeu-system --all-features qualify_file_commits_with_production_asset_decoder -- --ignored --nocapture
# Explicit layout observation.
cargo test --release -p prometeu-bytecode --test registry_v1 reference_map_probe -- --ignored --exact --nocapture
cargo test --release -p prometeu-bytecode --test registry_v0 reference_map_probe -- --ignored --exact --nocapture
```
Other ignored timing probes remain opt-in by their individual test names.
@@ -342,5 +334,5 @@ on that platform without lowering the existing floors.
No physical audio, eight-hour soak, packaged-installation or ignored manual
latency/layout qualification was selected by this gate. Prior manual observations
remain separate evidence. Current executable metadata and reports are emitted
under `target/quality-gate/` and `target/llvm-cov/` by every invocation.
remain separate evidence. Current coverage reports are emitted under `target/llvm-cov/`; CI retains execution
logs and build status.