Page History

...

1. BE Code Formatter: BE C++ code format check(sh build-support/check-format.sh)
2. FE Code Style Checker: FE JAVA code format check (cd fe/ && mvn clean install -DskipTests)
3. BE UT (Clang): Run BE unit test with Clang (DORIS_TOOLCHAIN=clang ./run-be-ut.sh --run --clean)
4. BE UT (macOS): Run BE unit test on macOS (./run-be-ut.sh --run --clean)
5. BE UT (Doris BE UT): BE unit tests will be executed: sh run-be-ut.sh --run
6. FE UT (Doris FE UT): FE unit tests will be executed: sh run-fe-ut.sh --run
7. License Check: License check, will check whether all source files contain Apache License Header
8. ShellCheck: Check all shell scripts format. (sh build-support/shell-check.sh)
9. Build Extensions / Build Broker: Build Broker (cd fs_brokers/apache_hdfs_broker/ && sh build.sh)
10. Build Extensions / Build Documents: Build Documents (cd docs && /bin/bash build_help_zip.sh)
11. P0 Regression (Doris Regression): Will execute the compilation of FE and BE (sh build.sh --fe --be), and build the Doris environment of 1 FE and 1 BE, and execute regression  p0 test(sh run-regression-test.sh --run)
12. P1 Regression (Doris Regression): Will execute the compilation of FE and BE (sh build.sh --fe --be), and build the Doris environment of 1 FE and 1 BE, and execute regression  p1 test(sh run-regression-test.sh --run)
13. Build Third Party Libraries (Linux): Build the third party libraries on Linux x86_64 (cd thirdparty && ./build-thirdparty.sh)
14. Build Third Party Libraries (macOS): Build the third party libraries on macOS x86_64 (cd thirdparty && ./build-thirdparty.sh)

The other Checks are NOT REQUIRED. Which means, even if these checks fail, it does not affect the merge of the Pull Request.

...