GitHub pull request #2505 of commit 390a00a61abdb5f54c43d6a165a2d375666f0210, no merge conflicts.
Started by user Alan Garny
Rebuilds build #1413
Running as SYSTEM
Setting status of 390a00a61abdb5f54c43d6a165a2d375666f0210 to PENDING with url https://autotest.bioeng.auckland.ac.nz/jenkins/job/OpenCOR_Windows/1414/ and message: 'Build started for merge commit.'
Using context: Windows
Building on master in workspace /home/jmaster/jenkins/jobs/OpenCOR_Windows/workspace
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/opencor/opencor.git # timeout=10
Fetching upstream changes from https://github.com/opencor/opencor.git
 > git --version # timeout=10
 > git --version # 'git version 2.7.4'
 > git fetch --tags --progress https://github.com/opencor/opencor.git +refs/pull/*:refs/remotes/origin/pr/* # timeout=10
 > git rev-parse refs/remotes/origin/pr/2505/merge^{commit} # timeout=10
Checking out Revision de77b454dd58e2cca29f450d98b5a130acd7efa4 (refs/remotes/origin/pr/2505/merge)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f de77b454dd58e2cca29f450d98b5a130acd7efa4 # timeout=10
Commit message: "Merge 390a00a61abdb5f54c43d6a165a2d375666f0210 into 51dd6c31a76eeff75884a265adeb3b25d60ddfdd"
First time build. Skipping changelog.
Triggering OpenCOR_Windows » Windows10
OpenCOR_Windows » Windows10 completed with result SUCCESS
Setting status of 390a00a61abdb5f54c43d6a165a2d375666f0210 to SUCCESS with url https://autotest.bioeng.auckland.ac.nz/jenkins/job/OpenCOR_Windows/1414/ and message: 'Build finished. '
Using context: Windows
Finished: SUCCESS