Unable to 'run' new projects due to ssh failure (publickey) about strider-github HOT 10 OPEN

FYI we're using the strider-github for adding projects

from strider-github.

It should work out of the box. Did you see the last comment on that PR? If you follow that, mainly step 2, does it help?

from strider-github.

Yes, I did try that..

from strider-github.

Ok, I think a revert is in order..

from strider-github.

let me double check if we have all the latest versions before you revert based on this issue

from strider-github.

we're on strider 1.7.6 and strider-github 2.3.1

from strider-github.

Ok, I'll try to do the revert later today. In the mean time, you can install strider-github 2.3.0 manually in your strider folder.

from strider-github.

FYI I It's working again after I installed 2.3.0
thanks for the help!

from strider-github.

Sorry for jumping on this so late. Yeah the issue is, the strider public key needs to be given access to the github repository.

One behavior we could implement out of the box (similar to what most hosted CI solutions do), so to add the public key as a deployment key to the repository on github.

The other use case in which we need to be able to install other private repositories while running the tests, one would need to create a machine user like this: https://documentation.codeship.com/faq/access-to-other-repositories-fails-during-build/

As you can see in this document for example, codeship by default adds a deployment key, and then if the use case requires access to multiple repos during running tests, then they have the documentation for that.

from strider-github.

@mandoz does this need to be documented? If so could you update the README.

from strider-github.