Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to 'run' new projects due to ssh failure (publickey) #70

Open
midgethoen opened this issue Jun 13, 2016 · 10 comments
Open

Unable to 'run' new projects due to ssh failure (publickey) #70

midgethoen opened this issue Jun 13, 2016 · 10 comments
Assignees
Labels

Comments

@midgethoen
Copy link

We've been using strider successfully for a while in our organization. However I noticed today that I cant 'run' newly added projects anymore, because of the following error:
Git clone failed with code 500

$ git clone --recursive [email protected]:getyippie/xxx.git . --branch master github 789ms -1
Cloning into '.'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists. 

some digging unveiled that previously added projects are using https and this one is using ssh. which led me to this pr #69

Is this supposed to work out of the box or do I need to manually add these keys?

@midgethoen
Copy link
Author

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

@knownasilya
Copy link
Member

knownasilya commented Jun 13, 2016

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?

@midgethoen
Copy link
Author

Yes, I did try that..

@knownasilya
Copy link
Member

Ok, I think a revert is in order..

@midgethoen
Copy link
Author

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

@midgethoen
Copy link
Author

we're on strider 1.7.6 and strider-github 2.3.1

@knownasilya
Copy link
Member

knownasilya commented Jun 13, 2016

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.

@midgethoen
Copy link
Author

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

@knownasilya knownasilya self-assigned this Jun 13, 2016
@mandoz
Copy link
Contributor

mandoz commented Sep 21, 2016

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.

@knownasilya
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants