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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semaphore CI thinks I'm ugly and says "fatal: I don't handle protocol ''https'" #8081

Closed
wants to merge 1 commit into
base: master
from

Conversation

4 participants
@cirosantilli
Contributor

cirosantilli commented Oct 18, 2014

It all started today when by accident I made a test that run:

git remote set-url origin "'https://gitlab.com/cirosantilli/gitlab-shell.git'"

(yes with double quotes)

on the toplevel (it touches the test system and was meant to run inside GitLab shell test clone folder...: #8051)

I run this test locally once then pushed.

Now, no matter what I do I get a CI error https://semaphoreapp.com/gitlabhq/gitlabhq/branches/pull-request-8081/builds/1 saying:

fatal: I don't handle protocol ''https'

even if I proceed like in this minimal PR for which I:

  • forked a clean GitLab
  • touch b && git add . && git commit -m b

Furthermore, it seems to be broken for every user: #8082 ... oops sorry!! 馃槻

b
@TeatroIO

This comment has been minimized.

TeatroIO commented Oct 18, 2014

I've prepared a stage. Click to open.

@cirosantilli cirosantilli changed the title from b to . Oct 18, 2014

@cirosantilli cirosantilli changed the title from . to Smaphore CI thinks I'm ugly and says "fatal: I don't handle protocol ''https'" Oct 18, 2014

@cirosantilli cirosantilli changed the title from Smaphore CI thinks I'm ugly and says "fatal: I don't handle protocol ''https'" to Semaphore CI thinks I'm ugly and says "fatal: I don't handle protocol ''https'" Oct 18, 2014

@Razer6

This comment has been minimized.

Member

Razer6 commented Oct 18, 2014

@cirosantilli I just wrote the semaphore team /cc @dosire

@rastasheep

This comment has been minimized.

rastasheep commented Oct 18, 2014

Hi guys, sorry for that, that change of origin's url have created issues with Semaphore, i have replayed to @Razer6's ticket with more info.

Caches with broken origin are now deleted, so building of project should be fine, before building this branch again please revert origin to git@github.com:gitlabhq/gitlabhq.gitto not mess up cache again.

Cheers,
Aleksandar from Semaphore team.

@cirosantilli

This comment has been minimized.

Contributor

cirosantilli commented Oct 18, 2014

@rastasheep thanks for such quick reply! Do you mean that you guys have already fixed the problem with a general patch that would prevent it from happening again? Is there an URL for the ticket you mention?

@rastasheep

This comment has been minimized.

rastasheep commented Oct 18, 2014

Yeah, it's fixed, just do not change origin url to HTTPS version, use SSH version instead. Also for this project (on GitHub) use GitHub origin url.

@cirosantilli

This comment has been minimized.

Contributor

cirosantilli commented Oct 18, 2014

It works! Closing.

@cirosantilli cirosantilli deleted the cirosantilli:edit-mr-v12 branch Oct 18, 2014

@rastasheep

This comment has been minimized.

rastasheep commented Oct 18, 2014

Great news, please let us know if you experience any other issue! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment