The recommended git tool is: NONE
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/sys_admin
> git init /home/jenkins/workspace/clubb_check_budget_balance_gfortran/sys_admin # timeout=10
Fetching upstream changes from https://github.com/larson-group/sys_admin
> git --version # timeout=10
> git --version # 'git version 1.8.3.1'
using GIT_ASKPASS to set credentials THe key used by the system for the tests
> git fetch --tags --progress https://github.com/larson-group/sys_admin +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/larson-group/sys_admin # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 4df474c504473c6d2306fad30ab9129faa68f5dd (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4df474c504473c6d2306fad30ab9129faa68f5dd # timeout=10
Commit message: "Final change to the deploy script sys_admin config fixing the post steps for all computers to allow full through run."
> git rev-list --no-walk 9c672f54d3fb0c316475258609ebd1c70b2d3bca # timeout=10