>> > > Turns out there is a bug in the git plugin to jenkins that the error > message is bad... ( > https://cloudbees.zendesk.com/hc/en-us/articles/205023034-Error-cloning-remote-repo-origin). > After checking the repo out by logging into the box it seems that someone > was on box modifying jenkins' workspace without fixing it:
Thanks for looking into the issues. > > [root@qa3 src]# git clean -dfx >> fatal: Not a git repository: >> /Users/mitsuhiko/Development/flask/.git/modules/docs/_themes > > > After blowing away the local checkout on the QA box-- its working just > fine. If you log onto QA boxes to manually do stuff, please make sure to > clean up after yourself (or maybe not make changes to the QA boxes' > workspaces ;) ). I doubt anyone has manually changed anything, considering I’m pretty much the only one doing stuff. Jenkins is awful, and the only way to actually get git to work is to have the job actually make a complete “clean” before every build (there’s a check box for that). If not, you’ll eventually end up in corruptions like this, I have no idea why, but it’s Jenkins for ya… Cheers, — leif
