Use Cases
Scheduled Nightly CI/CD Builds
Trigger nightly CI/CD pipeline builds with TrigRun. Automate test suites, dependency updates, and deployment verification on a cron schedule.
Trigger your CI/CD pipeline every night at midnight on weekdays. TrigRun calls your build API — GitHub Actions, GitLab CI, or a custom endpoint — so your nightly builds run reliably without maintaining a dedicated scheduling server.
The problem
You want a nightly build that runs the full test suite, checks for dependency vulnerabilities, and deploys to staging. CI platforms have built-in cron triggers, but they are often unreliable (GitHub Actions cron is best-effort and can be delayed by 15+ minutes) or don't support webhook-triggered flows.
The TrigRun solution
| Setting | Value |
|---|---|
| Schedule | 0 0 * * 1-5 (midnight, weekdays) |
| Method | POST |
| Timeout | 30 seconds (trigger only, not the build itself) |
| Retries | 3 attempts |
Trigger a GitHub Actions workflow
Expected results
Successful trigger:
| Field | Example value |
|---|---|
| Status | 204 No Content |
| Duration | 340 ms |
| Result | succeeded — GitHub Actions workflow dispatched |
GitHub API rate-limited:
| Field | Example value |
|---|---|
| Status | 429 Too Many Requests |
| Attempts | Retry after backoff |
| Result | succeeded on attempt 2 |
Other CI platforms
GitLab CI trigger
Custom build server
Common schedules
| Pattern | Expression | Use case |
|---|---|---|
| Weeknight midnight | 0 0 * * 1-5 | Standard nightly build |
| Every 6 hours | 0 */6 * * * | Continuous integration |
| Weekend regression | 0 2 * * 6 | Full regression suite Saturday night |
| Weekly dependency audit | 0 3 * * 1 | Security scanning Monday 3 AM |