Skip to content

Console Output

The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/clubb.git
 > git init /home/jenkins/workspace/clubb_api_commitment_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/clubb.git
 > 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/clubb.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/larson-group/clubb.git # 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 4db3def750df27785635939cbd300a9c77a2e1de (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4db3def750df27785635939cbd300a9c77a2e1de # timeout=10
Commit message: "Replacing the hardcoded path variables with larson-group.sh variable definitions, see here https://github.com/larson-group/sys_admin/blob/master/set_larson-group_paths/larson-group.sh)"
 > git rev-list --no-walk ad963d9b4c1272528c922a82966380a6e7135c2d # timeout=10