mirror of https://github.com/google/oss-fuzz.git
db8467bf30
Coverage builds need to be special cased since they aren't specified in sanitizers. Instead they are done for all C/C++ projects that use libFuzzer. Move all of this special casing to `should_build_coverage` and call that from `should_build` so we have one place where we decide this. Add tests as well. Fixes: https://github.com/google/oss-fuzz/issues/4371 |
||
|---|---|---|
| .. | ||
| base-images | ||
| build | ||
| ci | ||
| cifuzz | ||
| testcases | ||
| uploader | ||
| .pylintrc | ||
| README.md | ||
| bisector.py | ||
| bisector_test.py | ||
| build_specified_commit.py | ||
| build_specified_commit_test.py | ||
| helper.py | ||
| presubmit.py | ||
| repo_manager.py | ||
| repo_manager_test.py | ||
| templates.py | ||
| test_repos.py | ||
| utils.py | ||
| utils_test.py | ||
README.md
infra
OSS-Fuzz project infrastructure
Core infrastructure:
base-images- docker images for building fuzz targets & corresponding jenkins pipeline.
Continuous Integration infrastructure:
libfuzzer-pipeline.groovy- jenkins pipeline that runs for each OSS-Fuzz project.docker-cleanup- jenkins pipeline to clean stale docker images & processes.push-images- jenkins pipeline to push built base images.jenkins-cluster- kubernetes cluster definition for our jenkins-based build (not operational yet, #10).
helper.py
script to automate common docker operations
| Command | Description |
|---|---|
generate |
Generates skeleton files for a new project |
build_image |
Builds a docker image for a given project |
build_fuzzers |
Builds fuzz targets for a given project |
run_fuzzer |
Runs a fuzz target in a docker container |
coverage |
Runs fuzz target(s) in a docker container and generates a code coverage report. See Code Coverage doc |
reproduce |
Runs a testcase to reproduce a crash |
shell |
Starts a shell inside the docker image for a project |