The recommended git tool is: git
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/clubb.git
> git init /home/jenkins/workspace/clubb_cmake_test_branch # timeout=10
Fetching upstream changes from https://github.com/larson-group/clubb.git
> git --version # timeout=10
> git --version # 'git version 2.34.1'
> git fetch --tags --force --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/small_compile_update^{commit} # timeout=10
Checking out Revision 307cf9d78aa00cf5be10e3b6bc6f6197749046d6 (refs/remotes/origin/small_compile_update)
> git config core.sparsecheckout # timeout=10
> git checkout -f 307cf9d78aa00cf5be10e3b6bc6f6197749046d6 # timeout=10
Commit message: "Making compiler lookup a little more general, this allows us to compile on Derecho too. Now it uses LMOD_FAMILY_COMPILER by default, then tries FC as a backup, and has a map of names so that things like intel/intel-oneapi map to the same things. Also adding a toolchain for the cray compiler (cce)."