feat(ci): run quickstart stack test nightly with Slack failure alert#362
feat(ci): run quickstart stack test nightly with Slack failure alert#362marythought wants to merge 1 commit into
Conversation
The quickstart docker-compose stack test only runs on push/PR to static/quickstart/, tests/, and docs/getting-started/, so upstream breaking changes can silently break the quickstart with no signal. - Add a nightly schedule trigger (cron 17 6 * * *) - Add a Slack notification on failure, scoped to scheduled runs only (github.event_name == 'schedule'), so PR runs never touch the secret Requires a SLACK_WEBHOOK_URL repo secret (Incoming Webhook for #alerts-opentdf). Closes #355 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Mary Dickson <mary.dickson@virtru.com>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
The quickstart docker-compose stack test (
test-stackindocker-compose-test.yml) currently only runs on push/PR to paths understatic/quickstart/,tests/, anddocs/getting-started/. Upstream breaking changes (e.g. opentdf/platform#3563) can silently break the quickstart for new users with no notification.Changes
scheduletrigger —cron: '17 6 * * *'so the stack test runs daily.#alerts-opentdf, scoped to scheduled runs only (if: failure() && github.event_name == 'schedule').Prerequisite
A
SLACK_WEBHOOK_URLrepo secret must be added (Incoming Webhook for#alerts-opentdf). The Slack step is guarded toscheduleevents, so it never runs on PRs and the secret is not exposed to fork PRs.Closes #355