| 1 |
==================================== |
| 2 |
Continuous Integration Configuration |
| 3 |
==================================== |
| 4 |
|
| 5 |
The following pointers are aimed at maintainers to help describe a few points |
| 6 |
about the Cirrus CI setup that may not be obvious/intuitive. |
| 7 |
|
| 8 |
Email Notifications |
| 9 |
------------------- |
| 10 |
|
| 11 |
Cirrus CI doesn't feature any way to perform email notifications on failures, |
| 12 |
so that is instead handled by a separate GitHub Action: |
| 13 |
|
| 14 |
https://github.com/zeek/ci-email-action |
| 15 |
|
| 16 |
The configuration of that GitHub Action is typical: it's just the |
| 17 |
``.github/workflows/ci-notification.yml`` file, which set SMTP/mail info |
| 18 |
via secrets stored in GitHub for the repository: |
| 19 |
|
| 20 |
https://github.com/zeek/broker/settings/secrets |
| 21 |
|
| 22 |
The particular values used for those are currently from the Zeek project's AWS |
| 23 |
Simple Email Service configuration. |