Home Explore Help
Sign In
apache
/
hadoop
mirror of https://github.com/apache/hadoop.git
2
0
Fork 1
Files Issues 0 Wiki
Tree: c89d22d13a
Branches Tags
hadoop
/
hadoop-ozone
/
dev-support
/
checks
Doroszlai, Attila 8baebb54e1 HDDS-2171. Dangling links in test report due to incompatible realpath 5 years ago
..
README.md c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
_mvn_unit_report.sh 8baebb54e1 HDDS-2171. Dangling links in test report due to incompatible realpath 5 years ago
acceptance.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
author.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
blockade.sh 20064b69a8 HDDS-1978. Create helper script to run blockade tests. (#1310) 6 years ago
build.sh 6f25420f57 fixing ALL the checkstule issues under hadoop-ozone/dev-support/checks 6 years ago
checkstyle.sh 53637301d1 HDDS-2157. checkstyle: print filenames relative to project root (#1485) 5 years ago
findbugs.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
integration.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
isolation.sh 6f25420f57 fixing ALL the checkstule issues under hadoop-ozone/dev-support/checks 6 years ago
rat.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
shellcheck.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago
unit.sh c8d61ffef6 HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 5 years ago

README.md

Ozone checks

This directory contains a collection of easy-to-use helper scripts to execute various type of tests on the ozone/hdds codebase.

The contract of the scripts are very simple:

  1. Executing the scripts without any parameter will check the hdds/ozone project
  2. Shell exit code represents the result of the check (if failed, exits with non-zero code)
  3. Detailed information may be saved to the $OUTPUT_DIR (if it's not set, root level ./target will be used).
  4. The standard output should contain all the log about the build AND the results.
  5. The content of the $OUTPUT_DIR can be:
    • summary.html/summary.md/summary.txt: contains a human readable overview about the failed tests (used by reporting)
    • failures: contains a simple number (used by reporting)