Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document who should use ClusterFuzzLite and compare to other options #57

Open
jonathanmetzman opened this issue Nov 19, 2021 · 4 comments

Comments

@jonathanmetzman
Copy link
Collaborator

This was suggested by @WorksButNotTested

@hickford
Copy link

hickford commented Feb 5, 2022

It would be neat to have a table comparing ClusterFuzzLite and ClusterFuzz.

For example, is there any advantage adding ClusterFuzzLite if you are already using OSS-Fuzz?

@inferno-chromium
Copy link
Collaborator

@jonathanmetzman - We should update the docs on @hickford questions.

@hickford - If you are integrated with OSS-Fuzz and using CIFuzz [https://google.github.io/oss-fuzz/getting-started/continuous-integration/] in your CI/CD, then you don't need ClusterFuzzLite (CIFuzz and ClusterFuzzLite are same things). ClusterFuzzLite is for projects who can't use OSS-Fuzz, or have private repos.

@evverx
Copy link
Contributor

evverx commented Feb 9, 2022

If you are integrated with OSS-Fuzz and using CIFuzz [https://google.github.io/oss-fuzz/getting-started/continuous-integration/] in your CI/CD, then you don't need ClusterFuzzLite

FWIW I'm planning to replace CIFuzz with CFLite: google/oss-fuzz#7195 (comment) . In my experience CFLite is more stable and predictable.

@evverx
Copy link
Contributor

evverx commented Feb 9, 2022

I think it would be even more predictable if it was possible to pin it properly but considering that I already can pin the docker image used by CFLite to build the fuzzers I already can avoid issues caused by clang rolls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants