Changelog

You can now run BuildBuddy Workflows on a recurring schedule using standard cron expressions. This is useful for nightly builds, periodic integration tests, or any job that should run independently of code pushes or pull requests.

To schedule an action, add a schedule trigger with one or more cron expressions under triggers:

actions:
  - name: "Nightly tests"
    triggers:
      schedule:
        crons:
          - "0 2 * * *" # 2:00 AM UTC every day
    steps:
      - run: "bazel test //..."

Scheduled runs always execute against the latest commit on your repo's default branch. All cron times are interpreted as UTC, and the minimum supported interval between triggers is 15 minutes.

See the Workflows configuration docs for format details and more examples.

Starting June 1, 2026, BuildBuddy will automatically cancel in-progress Workflow runs when a newer run is triggered for the same action on a non-default branch. This helps avoid wasting resources on outdated runs when, for example, several commits are pushed in quick succession to a pull request branch.

This behavior only applies to non-default branches. Runs on your repo's default branch are not affected.

If you'd like to disable this behavior and allow concurrent runs for an action, set allow_concurrent_runs: true in the action's configuration.

See the Workflows configuration docs for more details.