Started by an SCM change
Obtained jenkins_tests/clubb_api_commitment_test/Jenkinsfile from git https://github.com/larson-group/clubb.git
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /home/jenkins/workspace/clubb_api_commitment_test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
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 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/master^{commit} # timeout=10
Checking out Revision f9d92113871bdf87b5e3147db6740ab654dc0967 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f9d92113871bdf87b5e3147db6740ab654dc0967 # timeout=10
Commit message: "Technically, the following two commits are not BFB"
 > git rev-list --no-walk 9371045e8739a4412dbe93f8948aacc9682d4852 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Run the API Commitment Script)
[Pipeline] sh
+ utilities/api_analysis/run_full_api_diagnostics.bash
###Checking out CLUBB###
Cloning into 'CLUBB'...