Is your feature request related to a problem? Please describe.
Current HammerDB CI/Pipeline automation is focused on Linux-based MariaDB workflows, meaning MariaDB benchmarking on Windows is not yet covered by the same repeatable, automated processes. This makes it harder to validate changes, compare results, and ensure consistency across supported platforms.
Describe the solution you'd like
Extend the existing HammerDB CI/Pipeline automation to support MariaDB on Windows, following the approach implemented for MariaDB on Linux in PR #860.
This should include:
- adding to the
ci.xml template for Windows MariaDB configuration and commands
- using PowerShell scripts instead of Bash for build and execution steps
- triggered by GitHub webhook, Web Service
Run Benchmark button, and cipush command
- clone, build and install MariaDB on Windows
- run HammerDB TPROC-C profile workloads
- capture results (NOPM, TPM, timings)
- generate comparison charts and CI output via the jobs framework
The aim is to provide consistent, repeatable MariaDB benchmarking on Windows aligned with existing CI/Pipeline workflows.
Describe alternatives you've considered
Manual benchmarking and ad-hoc scripting on Windows, but these do not provide the same level of consistency, repeatability or integration with the HammerDB jobs/CI framework.
Additional context
PR #860 (MariaDB CI automation for Linux) can be used as the reference implementation. The Windows version should follow the same structure, adapting build and execution steps to PowerShell.
Is your feature request related to a problem? Please describe.
Current HammerDB CI/Pipeline automation is focused on Linux-based MariaDB workflows, meaning MariaDB benchmarking on Windows is not yet covered by the same repeatable, automated processes. This makes it harder to validate changes, compare results, and ensure consistency across supported platforms.
Describe the solution you'd like
Extend the existing HammerDB CI/Pipeline automation to support MariaDB on Windows, following the approach implemented for MariaDB on Linux in PR #860.
This should include:
ci.xmltemplate for Windows MariaDB configuration and commandsRun Benchmarkbutton, andcipushcommandThe aim is to provide consistent, repeatable MariaDB benchmarking on Windows aligned with existing CI/Pipeline workflows.
Describe alternatives you've considered
Manual benchmarking and ad-hoc scripting on Windows, but these do not provide the same level of consistency, repeatability or integration with the HammerDB jobs/CI framework.
Additional context
PR #860 (MariaDB CI automation for Linux) can be used as the reference implementation. The Windows version should follow the same structure, adapting build and execution steps to PowerShell.