I forgot that this job tries to check all branches as well and I wonder if that is more of the cause. The credentials are stored within the local repository so multiple Git repos probably wouldn't cause conflicts. However, if a single repo checks out multiple branches, it of course does a git checkout so the same .git folder is used. I'm created some test jobs, one with multiple SCMs and one with a single SCM, both configured to check all branches. So far I've not seen these same issues. I still need to make sure the same version of Git is being used between the test jobs and the problem job.
I would also add that although it is intermittent, once it gets in this weird state it stays there until we manually run the job. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3b3bf0e4-d684-405e-bbd4-4a6a5b13746e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
