ci(perf): add the fixed Woodpecker G4 workflow
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/manual/performance Pipeline failed
ci/woodpecker/push/main Pipeline was successful

Move the push/PR pipeline to .woodpecker/main.yml so the repository can use
Woodpecker's multi-workflow directory. Add .woodpecker/performance.yml: manual
only, master only, on the single fixed Woodpecker agent (platform_id
woodpecker-agent-1). It builds one release binary, pins the first CPU in the
container cpuset, runs 5 warmups + 20 samples with --approved-node, and prints
the full marqdo.perf.v2 report plus a compact G4 summary for extraction.

No PR code is executed on the performance agent; the workflow is manual.
This commit is contained in:
cflmy committed 2026-11-21 19:51:09 +08:00
1 parent a9cc1729e1
commit a3f3ecf9d0
7 files changed
+66 -7

No files matched your search

+1 -1
View File
@@ -152,7 +152,7 @@ The remote SHA must be refreshed from CI after a push; do not read `c9f01aa8`
as the current tree.
This checkout's private remote is `https://git.cflmy.cn/cflmy/marqdo-cli` with
Woodpecker CI at `https://ci.cflmy.cn` (`.woodpecker.yml`). The Linux Docker
Woodpecker CI at `https://ci.cflmy.cn` (`.woodpecker/main.yml`). The Linux Docker
pipeline runs fmt/clippy/test/release-build; the docs-consistency gate runs in
`cargo test --workspace`. The GitHub-hosted native matrix is now green at
`5fcc111` ([run 30](https://github.com/cflmy/marqdo-cli/actions/runs/44896671929)).
+1 -1
View File
@@ -4,7 +4,7 @@
- Git remote: `https://git.cflmy.cn/cflmy/marqdo-cli.git`
- Woodpecker: `https://ci.cflmy.cn`
- Pipeline definition: [`.woodpecker.yml`](../.woodpecker.yml)
- Pipeline definition: [`.woodpecker/main.yml`](../.woodpecker/main.yml)
- Current hardening plan/RFC:
[`MARQDO_CI_SECURITY_PLATFORM_PERFORMANCE_RFC_20261121.md`](MARQDO_CI_SECURITY_PLATFORM_PERFORMANCE_RFC_20261121.md)
- Credentials are local-only and ignored; see
+2 -2
View File
@@ -41,12 +41,12 @@ curl -fsS -H "Authorization: Bearer $MARQDO_WOODPECKER_TOKEN" \
"$MARQDO_WOODPECKER_URL/api/user/repos"
```
CI itself is defined in `.woodpecker.yml`; the token is only for local API
CI itself is defined in `.woodpecker/main.yml`; the token is only for local API
queries/triggering, not for the pipeline. Configure any privileged secrets in
the Woodpecker repository settings, never in this repository.
## What is tracked
- `.woodpecker.yml` — public CI pipeline definition.
- `.woodpecker/main.yml` — public CI pipeline definition.
- this document — names/usage only, no values.
- `.secrets/` and `.env.local` — ignored local files.
+9 -2
View File
@@ -36,5 +36,12 @@ Rules enforced by the tool:
* Development-container smoke run (2026-11-21, `--warmups 1 --samples 3
--allow-smoke`): all nine workloads `VERIFIED`/`SMOKE`, no correctness
failures. Stored as a smoke artifact, **not** a release baseline.
* Remote G4: **UNVERIFIED** until a fixed self-hosted node runs
`.github/workflows/performance-linux.yml` with a fixed `--cpu-list`.
* Remote Woodpecker G4: the repository now has a manual
[`.woodpecker/performance.yml`](../.woodpecker/performance.yml) workflow on
the designated fixed agent (`platform_id: woodpecker-agent-1`). It runs
5 warmups / 20 samples, pins the first CPU in the container's
`Cpus_allowed_list`, and records the hardware/toolchain manifest. Trigger it
with the Woodpecker API using `"workflow": "performance"`; do not run it on
PR code. Its report is the G4 baseline for this node.
* GitHub G4: `.github/workflows/performance-linux.yml` remains available for a
physically separate node.