Skip to main content
Travis CI

Some builds are not being triggerred

Partial outage Lasted 55m · started · Travis CI's page

Level
confirmed
Worst impact
Partial outage
Components
Linux and Windows Builds
Down Index
28of 100

What to do

  • Check whether you use Travis CI Linux and Windows Builds. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 55m it lasted.

    Anything that failed between 2022-03-01 12:08 UTC and 2022-03-01 13:03 UTC may need a replay.
  • Subscribe to Travis CI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=travis-ci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Travis CI 3

  1. identified

    We have identified the issue where some of the builds are not being triggered and got an undetailed error when they are triggered.

    provider

  2. monitoring

    We have implemented the fix and monitoring the issue.

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-42267632b9

Is Travis CI still down?

No, this incident was resolved 2022-03-01 13:03 UTC. For Travis CI's live state, see https://down.guide/travis-ci.

How long did it last?

55m, from 2022-03-01 12:08 UTC to 2022-03-01 13:03 UTC, by the times Travis CI posted.

What was affected?

Travis CI named Linux and Windows Builds.

What caused it?

Travis CI hasn't published a root cause. If it does, it shows here.

Where does this come from?

Travis CI's official status page, https://www.traviscistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.