Yes, when I say my 2FA token, I meant my personal access token. I also
tried the Jenkins Credentials first before setting *git config --global
credential.helper wincred.*
On Tue, Sep 20, 2016 at 9:43 PM Baptiste Mathus wrote:
> +1. It's actually more than recommended, it's compulsory.
> With HTT
+1. It's actually more than recommended, it's compulsory.
With HTTPS on GitHub in that situation, you must use an access token. Using
your classical credentials won't work.
See
https://help.github.com/articles/which-remote-url-should-i-use/#when-2fa-is-enabled
(and the link mark already provided in
I've never tested the git plugin with wincred, so I don't know if it will
work.
If it does not work, you may need to remove your stored credentials
http://stackoverflow.com/questions/15381198/remove-credentials-from-git and
rely on the credentials mechanism inside Jenkins.
When you say that you e
I've been stuck on this problem for a couple of days and I cannot find any
resolution to this problem. Some of my colleagues suggest I use SSH to
clone my private repo, but I want to make sure I didn't miss something with
this setup. Hopefully, someone has encountered this issue before and was
