Runner can't access repository but does report broken builds everytime
Summary
Whenever a build is triggered we get the same output that it can't access the GitLabs repository. Our last good build was on the 10th of May and the day after (11th) all builds were broken onwards.
Steps to reproduce
Any build trigger for our repo.
Actual behavior
Running with gitlab-runner 10.8.0-rc2 (d954cadc)
on our-runner-name ff6fc208
Using Shell executor...
Running on our-runner-name...
Cloning repository...
Cloning into 'C:/Gitlab-Runner/builds/ff6fc208/0/ourorg/ourrepo'...
fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.com/ourorg/ourrepo.git/': error setting certificate verify locations:
CAfile: C:\Gitlab-Runner\builds\ff6fc208\0\ourorg\ourrepo.tmp\CI_SERVER_TLS_CA_FILE
CApath: none
The system cannot find the path specified.
Checking out 4c94f8c6 as some-commit-text...
fatal: Not a git repository (or any of the parent directories): .git
ERROR: Job failed: exit status 128
Expected behavior
A branch checkout and a build and test afterwards.
Relevant logs and/or screenshots
See Actual behavior.
Environment description
We're using our own runners on Windows using a shell.
Used GitLab Runner version
(I tried updating to see if that would fix it, we were using 10.7.2 when this issue occured)
gitlab-runner 10.8.0-rc2 (d954cadc)
Edited by 🤖 GitLab Bot 🤖