Companies / Travis CI / incidents
Travis CI: Build job errors when acquiring repository from GitHub (GitHub SSH key update)
Affected components: Builds Processing - Linux and Windows BuildsLinux and Windows BuildsGitHubThird Party Services - GitHubBuilds Processing - Mac Builds
Timeline of updates
- identified
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.
- monitoring
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.
- resolved
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.
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