Bitrise incident
Slow or hanging builds during clone and dependency resolution
Bitrise experienced a minor incident on July 14, 2026 affecting ⚙️ Builds (CI) and GitHub Git Operations, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 14, 2026, 03:35 PM UTC
We are currently investigating reports of slow or hanging builds. Affected builds may stall or take significantly longer than usual during early phases such as cloning repositories or resolving Swift Package Manager dependencies. We will provide a further update as soon as more information is available.
- investigating Jul 14, 2026, 03:36 PM UTC
We are continuing to investigate this issue.
- investigating Jul 14, 2026, 04:30 PM UTC
We are continuing to investigate this issue.
- resolved Jul 15, 2026, 06:10 PM UTC
This incident has been resolved. Some builds may still experience slower clone operations from GitHub due to performance degradation affecting Git operations in some of our datacenters. As a workaround, use Bitrise key-based caching for SPM dependencies so builds do not re-resolve them over the slow path. Add Restore SPM Cache (restore-spm-cache@3) before your dependency-resolution/build step and Save SPM Cache (save-spm-cache@1) after your dependency resolution and build steps — no extra configuration needed. Please note that Bitrise does not cache your source code; your repository must still be cloned to fetch the latest changes. If a build fails or hangs during code fetch, retry the build to attempt the clone operation again.