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.

Sign up for GitHub

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

Jump to bottom

lsremote() fails to configure credentials #222

Closed
progig opened this issue Apr 11, 2018 · 5 comments · Fixed by #223
Closed

lsremote() fails to configure credentials #222

progig opened this issue Apr 11, 2018 · 5 comments · Fixed by #223
Labels
bug
Milestone
2.1.2

Comments

@progig
Copy link

progig commented Apr 11, 2018

Hi,

When trying to use grgit.lsremote() a failure occurs:

Caused by: org.eclipse.jgit.errors.TransportException: https://myGitLabServer/myproject.git: Authentication is required but no CredentialsProvider has been registered.

I'm using Grgit version 2.1.1 with hardcoded credentials, grgit.push() and grgit.pull() just work fine.
Any idea why only lsremote() fails?
@ajoberstar ajoberstar added the bug label Apr 12, 2018
@ajoberstar ajoberstar added this to the 2.1.2 milestone Apr 12, 2018
@ajoberstar
Copy link
Owner

Woops... Looks like I forgot to configure the Transport in lsremote like I do in the other commands push.

Definitely a bug and nothing on your end.

@ajoberstar ajoberstar changed the title lsremote() fails lsremote() fails to configure credentials Apr 12, 2018
@progig
Copy link
Author

progig commented Apr 12, 2018

Thanks for the quick response, good to hear it's a bug, I was already pulling my hair out. ;-).
I'll wait for the fix!

ajoberstar added a commit that referenced this issue Apr 14, 2018
@ajoberstar
Configure credentials on lsremote
c38967d 
Credentials were not being configured on lsremote, unlike all other
TransportCommands that were being used.

This fixes #222.
@ajoberstar ajoberstar mentioned this issue Apr 14, 2018
Merged
@ajoberstar
Copy link
Owner

You can test the fix for this with 2.1.2-rc.1.

@progig
Copy link
Author

progig commented Apr 16, 2018

Hi Andrew,

Tested with 2.2.0-beta.1, lsremote() works again.
Thanks a lot!

@ajoberstar
Copy link
Owner

Thanks for testing. I'm pushing out 2.1.2 final (which includes this fix). 2.2.0 needs some more work (for other features).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
2.1.2
Development

Successfully merging a pull request may close this issue.

Configure credentials on lsremote ajoberstar/grgit
2 participants
@ajoberstar @progig