Our github admins recently turned off anonymous git access for public repos. As a result, several of our jenkins builds are having problems checking out their code.
I see a git-related “credentials” pull down in one of the jobs' configuration pages, and I've set my own creds on it, but it doesn't appear to be helping. I changed my password not long ago - I wonder if it's still trying to use my old password? Also, despite telling it to use my creds, it's still using: git -c core.askpass=true ls-remote -h https://github.intuit.com/DATA2/glitch-common.git HEAD ...which fails with: remote: Anonymous access to DATA2/glitch-common.git denied. Is there some way of telling Jenkins I have a new password? Does Jenkins fall back on anonymous access if a specific password doesn’t work? Any suggestions? Thanks! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/52a37605-0df6-46c3-b0c5-8d7752be097a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
