Build job errors when acquiring repository from GitHub (GitHub SSH key update)

What to do

• Check whether you use Travis CI GitHub, 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 6h 53m it lasted.

  Anything that failed between 2023-03-24 10:12 UTC and 2023-03-24 17:05 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. identifiedMar 24, 2023, 10:12 AM UTC

   Users utilizing Custom SSH Key in Travis CI private repository settings may experience build errors or warnings on git checkout. This is due main SSH keys being updated by GitHub (see https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/ ). We are working on updating our build environments configuration to utilize updated GitHub SSH keys. Users not utilizing Custom SSH keys are not affected.

   provider

2. monitoringMar 24, 2023, 12:47 PM UTC

   We have deployed hotfix replacing main Github host RSA SSH keys and are monitoring the builds. Users with Custom SSH Key in Travis CI repository settings should be able to build correctly now.

   provider

3. resolvedMar 24, 2023, 5:05 PM UTC

   The issue seems resolved. If you encounter further roadbloacks in repositories using Custom SSH Key in Travis CI, specifically on git repository cloning stage, please validate if a matching key pair is still available at GitHub. If not, removing old Custom SSH Key in Travis CI repository settings and regenerating the Custom SSH Key in Travis CI may help unblock your build jobs.

   provider

Corrections

None so far.

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