I have a GitHub repo that\'s big and contains several independently build-able bits. If I configure Jenkins with a job (or two) for each of these, I end up with having to pu
I had the same experience.
I have one job to pull the real remote repo, which is github.
Each of the other jobs (there are many) has a "Repository URL" like this:
file:///C:/Program Files (x86)/Jenkins/jobs/webtest-local-repo/workspace/.git
It clones fine, but subsequent fetches don't notice any changes.
The same issue presents in gitbash, so i guess this is a git issue, not a jenkins issue.
My horrific workaround was to make the dependent jobs delete their workspaces when finished building, so that every git operation is a "clone." It's ridiculous, but maybe less ridiculous than having a zillion jobs banging away at the same github repo.
ZOMG! That didn't work either, because while git could successfully clone the repo, jenkins would remember the previous revision and build the very same one again. Perhaps it's related to this issue, i dunno, i'm pretty fed up. We gave up, and now all the jobs poll github again. Maybe i'll get a hook working instead.