|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I can see a behavior change from 1.6.3 (ok) to 1.6.4 (fails to clone) when connecting to a private bitbucket repository using https. In the bitbucket case, I stored my bitbucket username and password in a Jenkins credential.
I don't see a behavior change from 1.6.3 (ok) to 1.6.4 (ok) when connecting to a private github repository using https. In the github case, I generated an access token and used my user name and that access token from a Jenkins credential.