Bitbucket: Pipelines not running entire script
Timeline of updates
- resolved
At 2:12AM UTC time, a mis-configured Docker agent image was propagated to our production cluster due to incorrect tagging. This caused builds to skip the clone step. We resolved the issue at 3:15 UTC time.
From Bitbucket’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on bitbucket.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Bitbucket, started 2016-11-24 03:29 UTC, resolved after 2.9 h, 1 update(s).
- Title
- Pipelines not running entire script
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/xbhn464jg6d6
Bitbucket profileRecent Bitbucket incidentsAll outages on November 24, 2016Bitbucket in November 2016MarkdownJSON