I have hit this behavior while building up a repo, outside of jenkins, so I think this is a problem with git itself.
Git handles relative paths in an heuristic way as described in comment comment-206652 and comment-188362. Which works for common use cases, you may be in a context or remote names and/or HEAD reference different from these cases.