The revocation function was unable to check revocation because the revocation server was offline.

Summary

Gitlab-runner can't clone the repo because revocation server was offline. I added http.schannelcheckrevoke=false config option to git, but sometimes job fails

Steps to reproduce

It can be reproduced only by making Windows revocation servers offline

.gitlab-ci.yml
ANY job

Actual behavior

Repository can't be cloned

Expected behavior

Repository is successfully cloned

Relevant logs and/or screenshots

job log
Fetching changes...
Reinitialized existing Git repository in C:/Gitlab-Runner/builds/1YJKD-Fq/0/repo/.git/
fatal: unable to access 'https://hostname/repo.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

Environment description

config.toml contents
Add your configuration here

Used GitLab Runner version

Running with gitlab-runner 13.5.0 (ece86343)
  on win-runner-2 1YJKD-Fq
Using Shell executor...

Possible fixes

Assignee Loading
Time tracking Loading