big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
bd498bac86
hadoop/hadoop-ozone/dev-support/checks
History
Doroszlai, Attila 2d81abce5e
HDDS-2265. integration.sh may report false negative 
Closes #1608
2019-10-09 16:17:40 +02:00
..
_mvn_unit_report.sh HDDS-2265. integration.sh may report false negative 2019-10-09 16:17:40 +02:00
acceptance.sh HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 2019-09-16 12:17:33 -07:00
author.sh HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 2019-09-16 12:17:33 -07:00
blockade.sh HDDS-2216. Rename HADOOP_RUNNER_VERSION to OZONE_RUNNER_VERSION in compose .env files. 2019-10-04 14:57:33 +02:00
build.sh fixing ALL the checkstule issues under hadoop-ozone/dev-support/checks 2019-07-12 11:30:56 +02:00
checkstyle.sh HDDS-2205. checkstyle.sh reports wrong failure count 2019-09-30 16:32:38 -07:00
findbugs.sh HDDS-2149. Replace findbugs with spotbugs 2019-09-26 22:56:05 -07:00
integration.sh HDDS-2251. Add an option to customize unit.sh and integration.sh parameters 2019-10-05 13:40:02 +02:00
isolation.sh fixing ALL the checkstule issues under hadoop-ozone/dev-support/checks 2019-07-12 11:30:56 +02:00
rat.sh HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 2019-09-16 12:17:33 -07:00
README.md HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 2019-09-16 12:17:33 -07:00
shellcheck.sh HDDS-2030. Generate simplifed reports by the dev-support/checks/*.sh scripts 2019-09-16 12:17:33 -07:00
unit.sh HDDS-2251. Add an option to customize unit.sh and integration.sh parameters 2019-10-05 13:40:02 +02:00

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)