Be more verbose when DNS fails for initial clone
When using heptapod-runner in a kubernetes that has a failing DNS or network problems, the error is a bit too generic, and might lead users to look for a bad solution.
abort: error: Try again by a more verbose version of the failure.
Also maybe don't try to enter
/builds/ if that step fails ?
Full log :
Running with gitlab-runner hpd-0.3.0 (cce91b92a7cb) on heptapod-runner-gitlab-runner-7f59666876-cwx4b Y-qn7xuL Preparing the "kubernetes" executor 00:00 Using Kubernetes namespace: heptapod-runner Using Kubernetes executor with image gcr.io/kaniko-project/executor:debug ... Preparing environment 00:03 Waiting for pod heptapod-runner/runner-y-qn7xul-project-380-concurrent-02rhz5 to be running, status is Pending Running on runner-y-qn7xul-project-380-concurrent-02rhz5 via heptapod-runner-gitlab-runner-7f59666876-cwx4b... Getting source from Git repository 00:06 Creating Mercurial repository abort: error: Try again Uploading artifacts for failed job 00:00 /bin/bash: line 116: cd: /builds/project/project: No such file or directory ERROR: Job failed: command terminated with exit code 1