title: GitLab Running - Unable to trust self signed certificate
body: <p>When running GitLab CI Runner I have to specify </p>
  
  <blockquote>
    <p>environment = ["GIT_SSL_NO_VERIFY=true"]"</p>
  </blockquote>
  
  <p>Without it I get the following error from GitLab CI</p>
  
  <pre><code>Cloning into 'D:/GitRunner/builds/c2RN8y5j/0/joeybob/mytestproect'...
  fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@myserver.local/joeybob/mytestproect.git/': error setting certificate verify locations:
    CAfile: D:\GitRunner\builds\c2RN8y5j\0\joeybob\mytestproect.tmp\CI_SERVER_TLS_CA_FILE
    CApath: none
  </code></pre>
  
  <p>Checking the contents of CI_SERVER_TLS_CA_FILE I can see that it matches the expected values between BEGIN CERTIFICATE and END CERTIFICATE.</p>
  
  <p>When I incude GIT_SSL_NO_VERIFY=true the CI window produces the following error but still succeeds </p>
  
  <pre><code>WARNING: Failed to load system CertPool: crypto/x509: system root pool is not available on Windows 
  ERROR: Failed to parse PEM in D:\GitRunner\builds\c2RN8y5j\0\joeybob\mytestproect.tmp\CI_SERVER_TLS_CA_FILE 
  </code></pre>
  
  <p>I assume there is something wrong with the PEM (crt) file. I'm running this on Windows Server 2016 and I exported the certificate from my local trusted root certificate store in the base-64 encoded X.509 format. Could this issue be to do with the way windows encodes the file?</p>