Skip to content

feat(ci): run quickstart stack test nightly with Slack failure alert#362

Open
marythought wants to merge 1 commit into
mainfrom
feat/quickstart-nightly-test
Open

feat(ci): run quickstart stack test nightly with Slack failure alert#362
marythought wants to merge 1 commit into
mainfrom
feat/quickstart-nightly-test

Conversation

@marythought

Copy link
Copy Markdown
Contributor

Summary

The quickstart docker-compose stack test (test-stack in docker-compose-test.yml) currently only runs on push/PR to paths under static/quickstart/, tests/, and docs/getting-started/. Upstream breaking changes (e.g. opentdf/platform#3563) can silently break the quickstart for new users with no notification.

Changes

  1. Nightly schedule triggercron: '17 6 * * *' so the stack test runs daily.
  2. Slack notification on failure — posts to #alerts-opentdf, scoped to scheduled runs only (if: failure() && github.event_name == 'schedule').

Prerequisite

A SLACK_WEBHOOK_URL repo secret must be added (Incoming Webhook for #alerts-opentdf). The Slack step is guarded to schedule events, so it never runs on PRs and the secret is not exposed to fork PRs.

Closes #355

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>
@marythought
marythought requested review from a team as code owners July 15, 2026 14:56
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@marythought, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0c411841-7026-4cf3-a03d-c41303999801

📥 Commits

Reviewing files that changed from the base of the PR and between 2b2b6b5 and 0fe0fa2.

📒 Files selected for processing (1)
  • .github/workflows/docker-compose-test.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/quickstart-nightly-test

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Successfully merging this pull request may close these issues.

feat: add nightly CI run for quickstart stack test with Slack alerts

1 participant