gitlab-8

gitlab-ci-multi-runner register gave me couldn't execute POST against https://xxxx/ci/api/v1/runners/register.json: Post https://xxxx/ci/api/v1/runners/register.json: x509: cannot validate certificate for xxxx because it doesn't contain any IP SANs Is there a way to disable certification validation ? I'm using Gitlab 8.13.1 and gitlab-ci-multi-runner 1.11.2. Based on Wassim's answer, and gitlab documentation about tls-self-signed and custom CA-signed certificates , here's to save some time if you're not the admin of the gitlab server but just of the server with the runners (and if the runner

We use gitlab ci with shared runners to do our continuous integration. For each build, the runner downloads tons of maven artifacts. Is there a way to configure gitlab ci to cache those artifacts so we can speed up the building process by preventing downloading the same artifact over and over again? Gitlab CI allows you to define certain paths, which contain data that should be cached between builds, on a per job or build basis (see here for more details). In combination with khmarbaise's recommendation, this can be used to cache dependencies between multiple builds. An example that caches all