Workaround for Cloning Errors with Github on Jenkins
Sometimes if a Github Repo is particularly large, the very first clone step can take a long time, and this makes it more likely to fail.
If your Jenkins clone keeps failing,
For example, I used to get an error message part way through a clone that looked like this:
Receiving objects: 14% (1846/12813), 903.98 MiB | 815.00 KiB/s
fatal: fetch-pack: invalid index-pack output