Bitbucket: Pipes within a pipelines step being executed in the wrong order
Timeline of updates
- resolved
We identified and rolled back an earlier bad release that caused pipes used within a pipelines step to be executed in the wrong order. The time of impact was from approximately 2022-05-06 02:50 - 5:30 UTC (affecting a percentage of users during that time). Any impacted pipelines can be re-run.
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 2022-05-06 06:24 UTC, resolved after 0 min, 1 update(s).
- Title
- Pipes within a pipelines step being executed in the wrong order
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/ymvfp830srht
Bitbucket profileRecent Bitbucket incidentsAll outages on May 6, 2022Bitbucket in May 2022MarkdownJSON