-users@googlegroups.com
Subject: Re: GitHub access using access token and Basic Authentication no
longer working
That's surprising, since those are the exact versions of the plugins which I
used and failed. I was using an API key and my user name (rather than my
actual password). The use
jenkinsci-users@googlegroups.com] *On Behalf Of *Chris Jansen
> *Sent:* Friday, April 11, 2014 5:00 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: GitHub access using access token and Basic Authentication
> no longer working
>
>
>
>
> Thanks Mark! Worked lik
Jansen
Sent: Friday, April 11, 2014 5:00 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: GitHub access using access token and Basic Authentication no
longer working
Thanks Mark! Worked like a charm.
Kevin, I agree it would have been helfpul if the plugin upgraded the URLs for
you. Another
Thanks Mark! Worked like a charm.
Kevin, I agree it would have been helfpul if the plugin upgraded the URLs
for you. Another nice-to-have would be for the plugin to lok for a basic
auth formatted URL on pull failure and generate a more informative error
message.
On Friday, April 11, 2014 12:
Another alternative would be for the plugin to automagically upgrade such URLs
and create suitable Credentials for them, so that the user gains the benefits
of the new method without their system getting broken.
- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-us
Kevin is correct. I duplicated the bug you're describing. A GitHub URL of
the form
https://username:passw...@github.com/github_username/github_repository does
not clone with the current version of the git client plugin (1.8.0) and the
current version of the git plugin (2.2.0).
If I take that sam
