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

Travis and git+ssh: github uris #972

Closed
vivienlacourba opened this issue Nov 16, 2016 · 7 comments
Closed

Travis and git+ssh: github uris #972

vivienlacourba opened this issue Nov 16, 2016 · 7 comments
Labels

Comments

@vivienlacourba
Copy link
Member

@marcoscaceres the WebRTC WG is using respec in its CI and since the change b8e09b8 (using git+ssh:// github uris) Travis now stops with a Permission denied error (see https://travis-ci.org/w3c/webrtc-pc/builds/176385617).
Can you revert or use https:// github uris instead ?

I am seeing this also broke respec's CI: https://travis-ci.org/w3c/respec/builds/176263945

You can reproduce the issue if you clone one of those repor with a user that don't have an SSH key registered in Github.

toto@han-solo:/tmp$ git clone git+ssh://git@github.com/isagalaev/highlight.js
Cloning into 'highlight.js'...
...
Warning: Permanently added 'github.com,192.30.253.113' (RSA) to the list of known hosts.
Permission denied (publickey).

copying @deniak @dontcallmedom

vivienlacourba added a commit to w3c/webrtc-respec-ci that referenced this issue Nov 16, 2016
Recent versions introduces issues with npm/yarn
but also with travis and git+ssh: uris see: w3c/respec#972
@marcoscaceres
Copy link
Member

Yep, sorry about that. Will fix today!

On 17 Nov. 2016, at 6:12 am, Vivien Lacourba notifications@github.com wrote:

@marcoscaceres the WebRTC WG is using respec in its CI and since the change b8e09b8 (using git+ssh:// github uris) Travis now stops with a Permission denied error (see https://travis-ci.org/w3c/webrtc-pc/builds/176385617).
Can you revert or use https:// github uris instead ?

I am seeing this also broke respec's CI: https://travis-ci.org/w3c/respec/builds/176263945

You can reproduce the issue if you clone one of those repor with a user that don't have an SSH key registered in Github.

toto@han-solo:/tmp$ git clone git+ssh://git@github.com/isagalaev/highlight.js
Cloning into 'highlight.js'...
...
Warning: Permanently added 'github.com,192.30.253.113' (RSA) to the list of known hosts.
Permission denied (publickey).
copying @deniak @dontcallmedom


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@vivienlacourba
Copy link
Member Author

Thx @marcoscaceres I'm also hoping you can release a new version including the switch back to npm (as yarn also brought some additional issues in our CI).

@marcoscaceres
Copy link
Member

@vivienlacourba, np... can you let me know what the issues are? I would still like to move back to yarn eventually, as it's hella fast during development ... when it works :)

@marcoscaceres
Copy link
Member

@vivienlacourba, ok, should be good now.

Be careful relying on the "develop" branch tho... it's deliberately unstable as it's where we do active development.

@marcoscaceres
Copy link
Member

Thx @marcoscaceres I'm also hoping you can release a new version including the switch back to npm (as yarn also brought some additional issues in our CI).

Released 6.1.3

@vivienlacourba
Copy link
Member Author

Thanks @marcoscaceres !

We usually use the stable gh-pages branch, but as we faced issues with yarn on travis I wanted to switch back to code that used npm and after seeing that you had already reverted respec to use npm in your latest commits I decided to give develop a shot.
Unfortunately it had the git+ssh uri problem reported in this issue.

Regarding the yarn+travis issue we faced it was a ENOENT error on a file in yarn's cache directory, sorry I don't have the travis logs anymore as I earlier re-ran all our failed builds after I reverted to a respec version that used npm.

vivienlacourba added a commit to w3c/webrtc-respec-ci that referenced this issue Nov 17, 2016
@marcoscaceres
Copy link
Member

@vivienlacourba, no problem. Seems a lot of people are running into the git+ssh problem.

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

2 participants