What problem does it solve?
Running Doris docker regression tests often fails because local edits to conf/ files or startup scripts contaminate the test environment, causing port conflicts, JDWP debug agent errors, or suites silently being skipped.
Core Features & Use Cases
- Clean Package Preparation: Sanitizes fe.conf, be.conf, and start_fe.sh from git HEAD so the docker image uses default ports and no debug agents.
- End-to-End Workflow: Covers environment checks, build, Docker image creation, regression configuration, and test execution via run-regression-test.sh.
- Troubleshooting Guidance: Maps common symptoms (0 suites found, JDWP errors, port conflicts) to concrete fixes.
- Use Case: A Doris developer modifies FE/BE code, builds with ./build.sh, and needs to validate the change against docker-based regression suites without interference from their local development configs.
Quick Start
Run the Doris docker regression suite for my latest build using a clean package sanitized from git HEAD.