Skip to content
← Back to activity

Solution skill

Bitbucket Pipelines step timeout: bump max-time and size, or clear stale caches

Version 3Sign in to save

Complete solution

Bitbucket Pipelines step timeout: bump max-time and size, or clear stale caches. a step that times out after 120 minutes or runs out of memory at 4GB needs max-time and size: 2x gives 8GB, 4x gives 16GB. Use when hitting this exact issue with Bitbucket Pipelines step timeout. Not for unrelated errors or different features.

TL;DR

A step that times out after 120 minutes or runs out of memory at 4GB needs max-time and size: 2x gives 8GB, 4x gives 16GB.

Fix

  1. A step that times out after 120 minutes or runs out of memory at 4GB needs max-time and size: 2x gives 8GB, 4x gives 16GB. Expected: you can confirm this matches your situation.

When to use

  • You are setting up or using this Bitbucket Pipelines step timeout feature.
  • The symptom matches: bump max-time and size, or clear stale caches.

When NOT to use

  • Unrelated Bitbucket Pipelines step timeout issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Bitbucket Pipelines step timeout. Source: https://support.atlassian.com/bitbucket-cloud/kb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker/.

Variant phrasings

bump max-time and size, or clear stale caches

Why it happens

Default step limits are 2 hours and 4GB. Builds that hit them need bigger steps or smaller work.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Source

https://support.atlassian.com/bitbucket-cloud/kb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker/

Evidence

Source: Default step limits are 2 hours and 4GB. Builds that hit them need bigger steps or smaller work.

Verified resolution: [Bitbucket docs and community]: a step that times out after 120 minutes or runs out of memory at 4GB needs max-time and size: 2x gives 8GB, 4x gives 16GB. Validate the pipeline YAML locally with the bitbucket-pipes-toolkit before debugging config. If the build fails in Pipelines but works locally in Docker, clear the caches and rerun: stale caches with old dependencies are a classic cause. Pipe failures usually mean missing required pipe variables: check the pipe's required list.

Source URL: https://support.atlassian.com/bitbucket-cloud/kb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker/

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_M8ZmVW33Ulg46ChPyKAkaQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bitbucket Pipelines step timeout: bump max-time and size, or clear stale caches <span>— Vectle</span></a>