Lines Matching full:cifuzz

11 OSS-Fuzz offers **CIFuzz**, a GitHub action/CI job that runs your fuzz targets
12 on pull requests. This works similarly to running unit tests in CI. CIFuzz helps
14 Currently, CIFuzz only supports projects hosted on GitHub.
18 CIFuzz builds your project's fuzzers from the source at a particular
19 pull request or commit. Then CIFuzz runs the fuzzers for a short amount of time.
20 If CIFuzz finds a crash, CIFuzz reports the stacktrace, makes the crashing
23 If CIFuzz doesn't find a crash during the allotted time, the CI test passes
24 (green check). If CIFuzz finds a crash, it reports the crash only if both of following are true:
31 CIFuzz only runs the fuzzers affected by a pull request/commit.
35 CIFuzz uses 30 day old/public regressions and corpora from OSS-Fuzz. This makes
46 You can integrate CIFuzz into your project using the following steps:
49 1. Copy the example [`main.yml`](https://github.com/google/oss-fuzz/blob/master/infra/cifuzz/exampl…
67 name: CIFuzz
75      uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
80      uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
103 `fuzz-time`: Determines how long CIFuzz spends fuzzing your project in seconds.
108 `dry-run`: Determines if CIFuzz surfaces errors. The default value is `false`. When set to `true`,
109 CIFuzz will never report a failure even if it finds a crash in your project.
126 name: CIFuzz
138      uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
144      uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
161 You can make CIFuzz trigger only on certain branches or paths by following the
163 For example, the following code can used to trigger CIFuzz only on changes to
167 name: CIFuzz
185      uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
190      uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
203 You can checkout CIFuzz configs for OSS-Fuzz projects. Example -
204 [systemd](https://github.com/systemd/systemd/blob/master/.github/workflows/cifuzz.yml),
209 The results of CIFuzz can be found in two different places.
212     1. This log can be accessed in the `actions` tab of a CIFuzz integrated repo.
213     1. Click on the `CIFuzz` button in the workflow selector on the left hand side.
223     1. When a crash is found by CIFuzz the Upload Artifact event is triggered.
235 …tps://github.com/google/oss-fuzz/issues/new) if you have questions or any other feedback on CIFuzz.