Skip to content

PMM-13487 A pipeline to build PMM anywhere#5040

Draft
ademidoff wants to merge 41 commits intov3from
PMM-13487-a-pipeline-to-build-pmm
Draft

PMM-13487 A pipeline to build PMM anywhere#5040
ademidoff wants to merge 41 commits intov3from
PMM-13487-a-pipeline-to-build-pmm

Conversation

@ademidoff
Copy link
Copy Markdown
Member

PMM-13487

This pull request introduces a new Docker-based build pipeline for PMM (Percona Monitoring and Management), replacing the previous RPM/YUM-based installation approach. The changes include new Dockerfiles for building both server and client images, configuration files for environment and build context management, and updates to Ansible roles to reflect the new build process. The most important changes are grouped below.

New Docker-based Build Pipeline:

  • Added Dockerfile.server, which implements a multi-stage build for PMM Server, building all major components (pmm-managed, grafana, victoriametrics, dashboards, etc.) from source and copying the resulting binaries and assets directly into the runtime image, replacing RPM-based installation.
  • Added Dockerfile.client for building the PMM Client image, installing necessary dependencies, extracting the client tarball, and setting up the runtime environment.
  • Added Dockerfile.builder for a Go build environment used in the pipeline.

Build Context and Environment Management:

  • Introduced .dockerignore to optimize Docker build context by excluding unnecessary files and directories.
  • Added .env.example to define environment variables for build-time configuration, including refs for all major dependencies and Minio S3 cache settings.
  • Added .gitignore for pipeline-specific build outputs and cache files.

Ansible and Legacy Build Cleanup:

  • Removed tasks from pmm-images Ansible role that previously set up a local YUM repository and installed PMM Server components via RPMs, as binaries are now copied directly in the Dockerfile. [1] [2]

Development Environment Improvements:

  • Updated .devcontainer/setup.py to allow both trust and scram-sha-256 authentication methods in pg_hba.conf for PostgreSQL in the dev environment, improving developer convenience.

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.79%. Comparing base (c8246ba) to head (0df5e1e).

Additional details and impacted files
@@            Coverage Diff             @@
##               v3    #5040      +/-   ##
==========================================
+ Coverage   47.76%   47.79%   +0.03%     
==========================================
  Files         410      410              
  Lines       41967    41967              
==========================================
+ Hits        20045    20059      +14     
+ Misses      19944    19931      -13     
+ Partials     1978     1977       -1     
Flag Coverage Δ
admin 35.80% <ø> (ø)
agent 53.36% <ø> (+0.11%) ⬆️
managed 47.71% <ø> (+<0.01%) ⬆️
vmproxy 72.09% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant