mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
04c3c2ec72
This feels more like a band-aid solution - it still requires very manual intervention to get the next builds, but at least this way we don't rely on whatever Clang/libc++ happens to ship with FreeBSD for the only libc++ testing. It seems like sanitizer builds don't use libc++, but I'd rather a dedicated Linux/Clang/libc++ task at least. |
||
|---|---|---|
| .. | ||
| alpine | ||
| centos-stream-9 | ||
| debian-11 | ||
| debian-12 | ||
| fedora-39 | ||
| fedora-40 | ||
| freebsd | ||
| macos | ||
| opensuse-leap-15.5 | ||
| opensuse-leap-15.6 | ||
| opensuse-tumbleweed | ||
| ubuntu-20.04 | ||
| ubuntu-22.04 | ||
| ubuntu-24.04 | ||
| windows | ||
| benchmark.sh | ||
| build.sh | ||
| collect-repo-info.py | ||
| common.sh | ||
| container-images-tag-and-push.sh | ||
| find-current-version.sh | ||
| init-external-repos.sh | ||
| pre-build.sh | ||
| public-ecr-cleanup.sh | ||
| README | ||
| spicy-install-analyzers.sh | ||
| test-fuzzers.sh | ||
| test.sh | ||
| tsan_suppressions.txt | ||
| update-zeekygen-docs.sh | ||
| upload-coverage.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 Organization-Level Secured Variable in Cirrus CI settings at https://cirrus-ci.com/settings/github/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 the ``.github/workflows/ci-notification.yml`` file, which sets SMTP/mail info via secrets stored in GitHub for the Zeek organization: https://github.com/organizations/zeek/settings/secrets The particular values used for those are currently from the Zeek project's AWS Simple Email Service configuration.