Companies / Travis CI / incidents

Travis CI: Builds are not triggering for travis-ci.com

Impact: majorStatus: postmortemStarted Resolved (1.0 h)5 updatesSource: stspg.io (opens in new tab)
Summary

Travis CI’s major outage prevented travis-ci.com Linux and Windows builds from triggering from 2020-09-24 09:12 UTC to 2020-09-24 10:14 UTC (1 h 1 min). The postmortem cited a Bitbucket implementation infinite loop involving suspended users or missing repository permissions, causing VCS instability and high memory usage; the fix checks the suspended flag.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Builds Processing - Linux and Windows BuildsLinux and Windows Builds

Timeline of updates

  1. investigating

    We are investigating the root cause behind why builds are not triggered for travis-ci.com

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented and we are monitoring the results.

  4. resolved

    This incident has been resolved.

  5. postmortem

    We are extremely sorry about the outage on this incident and we would like to share some action that has been taken; * Issue reported date: The issue has been reported on 24.09.2020 09:12 UTC. * Issue: **Unstable VCS service, high memory usage** * Reason: Issue in Bitbucket implementation, infinity loop when a user has been suspended or without permissions to the repository * Solution: Check suspended flag before API calls, infinite loop retries removed. * Fixed time: 24.09.2020 10:14 UTC * Action required from users: None * Issue status: Fixed Thank you for your understanding.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Travis CI profile · Recent Travis CI incidents · Markdown · JSON