aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLeo Neat <lneat@google.com>2020-03-18 10:58:08 -0700
committerGitHub <noreply@github.com>2020-03-18 10:58:08 -0700
commitd7a4a4b89fa61d7d5f6dc975154b2c2ffbfde796 (patch)
tree40cbeb10b3b3059695f7c8a0b7487260e4ac49da /docs
parentf8cd51117f34a420f693b1486f4351c47d8e8900 (diff)
downloadoss-fuzz-d7a4a4b89fa61d7d5f6dc975154b2c2ffbfde796.tar.gz
Documentation update (#3518)
Just fixing a few spelling mistakes and added some features to the description.
Diffstat (limited to 'docs')
-rw-r--r--docs/getting-started/continuous_integration.md14
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/getting-started/continuous_integration.md b/docs/getting-started/continuous_integration.md
index 7e128d663..bec1c5a8e 100644
--- a/docs/getting-started/continuous_integration.md
+++ b/docs/getting-started/continuous_integration.md
@@ -14,11 +14,15 @@ fix bugs before they make it into your codebase
## How it works
-CIFuzz works by checking out a repository at the head of a pull request. The
-project's fuzz targets are built and run for
-a definite amount of time (default is 10 minutes). If a bug is found, the
-stack trace as well as the test case are made abailable for download.
- If a crash is not found the test passes with a green check.
+CIFuzz works by checking out a repository at the head of a pull request. For projects
+that support code coverage, fuzzers coverage is compared with PR diffs to determine
+which fuzzers should be used. For projects that do not support code coverage, all
+fuzzers are run for an even length of time. If no bugs are found and the allotted
+time is up (default is 10 minutes), the CI test passes with a green check. But
+if a bug is found, the bug is checked for reproducability and against
+old OSS-Fuzz builds to prevent the reporting of pre-existing bugs. If the bug is both
+new and reproducible, it is reported and the
+stack trace as well as the test case are made available for download.
## Requirements