mirror of
https://github.com/zeek/zeek.git
synced 2025-10-04 07:38:19 +00:00
82978a8860
* origin/topic/jsiwek/fuzzing: Use zeek::detail namespace for fuzzer utils Set terminating flag during fuzzer cleanup Add missing include to standalone fuzzer driver Improve standalone fuzzer driver error messages Test fuzzers against seed corpus under CI ASan build Update fuzzing README with OSS-Fuzz integration notes Link fuzzers against shared library to reduce executable sizes Improve FuzzBuffer chunking Fix compiler warning in standalone fuzzer driver Adjust minor fuzzing documentation Exit immediately after running unit tests Add OSS-Fuzz Zeek script search path to fuzzers Assume libFuzzer when LIB_FUZZING_ENGINE file doesn't exist Change handling of LIB_FUZZING_ENGINE Change --enable-fuzzing to --enable-fuzzers Add standalone driver for fuzz targets Add basic structure for fuzzing targets |
||
|---|---|---|
| .. | ||
| centos-7 | ||
| debian-9 | ||
| debian-9-32bit | ||
| fedora-30 | ||
| freebsd | ||
| macos | ||
| ubuntu-16.04 | ||
| ubuntu-18.04 | ||
| build.sh | ||
| init-external-repos.sh | ||
| README | ||
| test-fuzzers.sh | ||
| test.sh | ||
========================================= Continuous Integration Configuration Info ========================================= The following pointers are aimed at maintainers to help describe a few points about the Cirrus CI setup that may not be obvious/intuitive. Private Test Suite ------------------ Access to the private test suite is available in CI tasks except in Pull Requests from people that do not otherwise have write access to the zeek repository on GitHub. To configure this access for the ``zeek-testing-private`` repository, it uses a "deploy key" which is a single purpose SSH key with read-only permissions. Here's how it can be set up: 1. ``ssh-keygen -f cirrus-key`` 2. Add contents of ``cirrus-key.pub`` as a new key on GitHub: https://github.com/zeek/zeek-testing-private/settings/keys 3. Generate a new Cirrus CI secured variable in the repository settings at https://cirrus-ci.com/github/zeek/zeek. The value of the secured variable is the base64-encoded private key, and can be obtained from the output of the command: ``base64 cirrus-key``. 4. Take the ``ENCRYPTED[...]``` string generated by Cirrus and use that as the value of ``ZEEK_TESTING_PRIVATE_SSH_KEY`` in ``.cirrus.yml`` 5. Delete the local key: ``rm cirrus-key*`` 6. Commit/push the changes. Email Notifications ------------------- Cirrus CI doesn't feature any way to perform email notifications on failures, so that is instead handled by a separate GitHub Action: https://github.com/zeek/ci-email-action The configuration of that GitHub Action is typical: it's just the ``.github/workflows/ci-notification.yml`` file, which set SMTP/mail info via secrets stored in GitHub for the Zeek repository: https://github.com/zeek/zeek/settings/secrets The particular values used for those are currently from the Zeek project's AWS Simple Email Service configuration.