PMM-14804 Build server components as binaries instead of RPMs

[talhabinrizwan]

https://jira.percona.com/browse/PMM-14804

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4475-8794885
Client docker: perconalab/pmm-client-fb:PR-4475-8794885
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4475-8794885
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-8794885.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4475-8794885&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-8794885.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6768/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4475-8bfc46a
Client docker: perconalab/pmm-client-fb:PR-4475-8bfc46a
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4475-8bfc46a
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-8bfc46a.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4475-8bfc46a&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-8bfc46a.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7429/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4475-c726b6f
Client docker: perconalab/pmm-client-fb:PR-4475-c726b6f
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4475-c726b6f
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-c726b6f.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4475-c726b6f&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-c726b6f.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7430/

[travagliad]

FB Tests triage — PMM-T430 - Verify metrics on MySQL Group Replication Summary Dashboard @pmm-ps-integration (the only failing job in run 2696, and again in run 2697) reproduces deterministically — it is not a flake, not your change, and not a pmm-qa test bug. The cause is that the percona/pmm branch this FB builds from is stale: percona/pmm#5767 (PMM-15308, merged 2026-09-18) trimmed the trailing spaces from three GR dashboard panel titles, and percona/pmm-qa#1449 trimmed the matching test expectations the same day — but ci.py clones the feature branch directly without merging main, and PMM-14804-build-binaries-only has a merge-base of 2026-09-17, so the image still ships "Applied Transactions " with the trailing space.

Reproduced on a throwaway VM against the exact image perconalab/pmm-server-fb:PR-4475-8bfc46a: its Grafana API serves 'Applied Transactions ', so the shipped locator //section[@data-testid="data-testid Panel header Applied Transactions"] matches 0 elements (hence the 60 s waitFor timeout). On perconalab/pmm-server:3-dev-latest (built after the trim) the same locator matches 1, and PMM-T430 passes in 33 s with the same GR setup — so no pmm-qa fix is warranted.

Action: merge/rebase main into percona/pmm branch PMM-14804-build-binaries-only and rebuild the FB. Re-running the failed job will not help — it reuses the same pinned image.

---

Generated by Claude Code

[travagliad]

FB triage — the single red check (E2E / Percona Server for MySQL UI integration tests / @pmm-ps-integration, run 35571101067) is not a flake and is not caused by the substance of your change: PMM-T430 - Verify metrics on MySQL Group Replication Summary Dashboard failed all 3 attempts here and all 3 in the 06:22 run, byte-identically, while the same test passes in ~25 s on every other recent FB. The panels do have data — the run's own Playwright trace shows the Applied Transactions query (mysql_perf_schema_transactions_remote_applied_total) returning values ~20 s before the failing wait even starts; what fails is the exact-match locator, because this build's dashboards still carry the old panel titles with a trailing space (data-testid Panel header Applied Transactions ), whereas pmm-qa main now expects the trimmed titles after percona/pmm-qa#1449 — the QA half of percona/pmm#5767 (PMM-15308, merged 2026-09-18 14:49 UTC).

Your pmm branch PMM-14804-build-binaries-only (fd686ff) diverged from main on 2026-09-17 and is missing that commit, so the image under test still ships "title": "Applied Transactions ". Merging main into PMM-14804-build-binaries-only and rebuilding the FB should turn this check green — no pmm-qa fix and no product ticket are needed. I deliberately did not spend a job re-run: it would reuse the same pinned PR-4475-c726b6f image and fail identically.

---

Generated by Claude Code

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4475-0b0c2e8
Client docker: perconalab/pmm-client-fb:PR-4475-0b0c2e8
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4475-0b0c2e8
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-0b0c2e8.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4475-0b0c2e8&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4475-0b0c2e8.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7530/