I have a pipeline that runs a pre-build stage that builds four VS projects in a single
Lib:pre-build: job that saves the output directories as artifacts, approx 150MB. I am then running approx. 20 build jobs in a build stage that download these artifacts so they’re not re-built by those 20 solutions.
The pre-build jobs set the output directories as artifacts, the build jobs have
dependencies: ["Lib:pre-build"] set to download just these artifacts.
I have two GitLab runners running on Windows, one in AWS and one on-premises. All the 20 build jobs are succeeding but taking too long as they are all getting errors downloading the 150MB artifacts from the previous stage:
Downloading artifacts for <edited>... Runtime platform arch=amd64 os=windows pid=9196 revision=8925d9a0 version=14.1.0 ERROR: Downloading artifacts from coordinator... error couldn't execute GET against https://gitlab.com/api/v4/jobs/<edit>/artifacts?direct_download=true: Get https://storage.googleapis.com/gitlab-gprd-artifacts/<edit>: x509: certificate signed by unknown authority id=<edit> token=<edit> WARNING: Retrying... error=invalid argument Downloading artifacts from coordinator... ok id=<edit> responseStatus=200 OK token=<edit>
This issue downloading artifacts is holding up some jobs by up to 10mins.
I can’t find any information on how or why I’d need to deal with gitlab.com (or googleapis.com) certificates when registering or using a gitlab runner. It seems to me this is an issue with gitlab.com?