Bug: `curl` on Jenkins executor fails to resolve host

Summary

Executing curl in a shell script as build task on Jenkins sometimes results in an error curl: (6) Could not resolve host

Steps to reproduce

Not really deterministically reproducible, it happens every now and then. We have a build job where we download a shell script from Github via curl and execute it. This is much faster than cloning the entire repo.

What is the current bug behavior?

Sometimes it seems as if DNS resolution to raw.githubusercontent.com fails, resulting in an error with curl

What is the expected correct behavior?

curl should be able to download the file without failures.

Relevant logs and/or screenshots

this is the build job. Tried it with wget as well - same problem.

I have never witnessed that behaviour when cloning the repo instead of downloading the file.

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

We can use a fallback, which is to checkout the entire repository that contains the shell script. While it achieves the same result, it is much slower than simply downloading the file.