Bitbucket "Your build exceeded the maximum build time"

By Daniel Zoghalchali·Latchkey

A step ran longer than its build-time limit (120 minutes by default, configurable via max-time) and Bitbucket killed it. The step is stopped mid-run, not failed by your code.

What this error means

A step is terminated with "Your build exceeded the maximum build time and was stopped." The logs simply cut off where the limit hit - there is no error from your own command.

Your build exceeded the maximum build time and was stopped.

Common causes

The step genuinely takes too long

A slow test suite, large build, or heavy install can exceed the default 120-minute cap (or a lower max-time you set).

A hang or deadlock

A command waiting on input, a deadlocked test, or a process that never exits will run until the limit and then be killed.

How to fix it

Raise the step max-time

Set max-time (in minutes) on the step or globally. The cap depends on your plan; you cannot exceed the plan maximum.

pipelines:
  default:
    - step:
        name: Slow tests
        max-time: 120
        script:
          - ./run-tests.sh

Split and parallelize the work

Break one long step into parallel steps so each finishes well under the limit.

- parallel:
    - step: { script: [ ./test.sh unit ] }
    - step: { script: [ ./test.sh integration ] }

Find and fix the hang

1. Add timeouts to network calls and test runners so a hang fails fast.
2. Ensure no command waits on stdin in CI.
3. Cache dependencies so install time does not eat the budget.

How to prevent it

• Cache dependencies and build outputs to cut step duration.
• Parallelize long test suites across steps.
• Add per-command timeouts so hangs surface quickly.

Frequently asked questions

Related guides

References

• GitHub Actions documentation