Hello everyone, Recently some builds on the private repos of the organisation I work for started to fail. The problem seems to be related to a wrong SSH key being loaded by the travis build. While before the following message was printed: Installing SSH key from: repository settings Now the fol…

Just got a reply from the support: This change has been rolled back for private repositories.

Both our builds have the same config but some of them ignore the repo key and switch back to the default repo key. This started last friday, was there a recent change to the travis config api? Seems like a bug. Why is my ssh key being ignored when its on the settings tab of a specific build? Broken…

We are also facing the same issue. As a workaround, I have tried adding the encrypted key to .travis.yml, but the build is not able detect the environment variables. It happens only for the pull requests. openssl aes-256-cbc -K $encrypted_xxxxx_key -iv $encrypted_xxxxx_iv -in travis_deploy_key.en…

That lines up with when ours started doing the exact same thing. Same thing from build logs as well. Even though a key is defined in repo settings, its using the “default repository key” instead. Confirmed via debug build and comparing.

cycling your secrets is something that all users should do on a regular basis. If you are unsure how to do this please contact Support. We cycled our keys as recommended by the security bulletin but that does not work either. It seems like ssh key variables are plain broken at the moment.

[image] Questions on security bulletin (repository secrets leak to PRs) Travis CI Discussions & Feedback This is regarding the recent security bulletin: Security Bulletin What was the total window of exposure? It’s good to know you started patching on Sept 3, but that do…

Sadly, all of our repo’s are private, and should not be affected by this.

I am also facing the same issue and our repo’s are private as well.

Same problem since 2 days, the support is silent. It’s awful.

(paid travis-ci.com user) We have a Github private repo in our Org that includes a submodule from a public repo, also from our Org. PR and deployment builds are failing, either at the submodule init or at the hosted Dev/Stage environment for develop-build or master-build. This has halted the code de…

Travis CI build not loading correct SSH key

Travis CI Discussions & Feedback

bmartinez287 September 14, 2021, 8:20pm 8

Good insights.

Topic		Replies	Views
You have ssh keys defined for your repositories, please review their settings now. The new share ssh keys with forks (PRs) repository setting are present and set to on for repositories already in travis CI in order to not break existing builds Feature Requests	1	1557	November 3, 2023
Can't find SSH keys settings under Travis project settings Travis CI Discussions & Feedback	4	1547	November 16, 2021
Trying to get Travis CI to work with SSH Key w/o signing into Github Travis CI Discussions & Feedback build-env	6	1503	November 14, 2018
Migrating Deploy SSH keys from personal repo to organisation repo Travis CI Discussions & Feedback github , travis-build	4	720	July 24, 2020
Travis-ci.org - build cannot clone private Bitbucket repository Atlassian Bitbucket	2	3138	April 13, 2020

Travis CI build not loading correct SSH key

Related topics