mirror of https://github.com/google/oss-fuzz.git
![]() This can be useful for artifacts we want to upload that we know do not need to be tarred, such as crashes. It's important not to tar these because they will need to be viewed by users. |
||
---|---|---|
.. | ||
base-images | ||
build | ||
ci | ||
cifuzz | ||
triage-party | ||
uploader | ||
.dockerignore | ||
README.md | ||
bisector.py | ||
bisector_test.py | ||
build_fuzzers.Dockerfile | ||
build_specified_commit.py | ||
build_specified_commit_test.py | ||
helper.py | ||
helper_test.py | ||
presubmit.py | ||
pytest.ini | ||
repo_manager.py | ||
repo_manager_test.py | ||
retry.py | ||
run_fuzzers.Dockerfile | ||
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 |