Having failing build because of a network issues is annoying and harms bazels reputation as a reliable build system.
Rules will use ctx.download(url, ...)
. Could bazel track the urls that rules tried to download from and output them together with the rule that triggered the download.
What about some tooling that helps to add mirror urls to improve reliability or generate a list of unmirrored urls + licenses to setup mirroring?
Alternatively, I'd like to have a capability which allows to rewrite outgoing URLs.
For example:
http[s]://*.maven.org/maven2/
--> `https://my.internal.mirror/some/pathI'm looking for this option as well.
I am currently surviving with --distdir.. but the bazel internal dependencies are getting a headache to update when bazel versions change.
Is there any workaround to this at the moment? This makes maintaining internal bazel dependencies difficult as each dep has to either be maintained locally or the WORKSPACE has to be littered with http_archive rules that point to the internal mirror.
Most helpful comment
Alternatively, I'd like to have a capability which allows to rewrite outgoing URLs.
For example:
http[s]://*.maven.org/maven2/
--> `https://my.internal.mirror/some/path