what's up with https://mirror.bazel.build #139
Comments
|
I'm not exactly sure. I think it's a bit of a manual setup at the moment, so it's neither well documented nor available for general use. I don't even think all current mirror entries in our WORKSPACE are populated. I can try and have that fixed for Lab, but I don't think it's open to arbitrary new submissions. |
thufschmitt
added a commit
to tweag/rules_haskell
that referenced
this issue
Mar 10, 2020
The mirrored protobuf archive from `https://mirror.bazel.build` now returns a 404. Given that mirror.bazel.build is undocumented thing that seems only used by internal google products and with no guaranty at all − see google-deepmind/lab#139 −, I don't think keeping these mirrors give a lot of value anyways.
mboes
pushed a commit
to tweag/rules_haskell
that referenced
this issue
Mar 16, 2020
The mirrored protobuf archive from `https://mirror.bazel.build` now returns a 404. Given that mirror.bazel.build is undocumented thing that seems only used by internal google products and with no guaranty at all − see google-deepmind/lab#139 −, I don't think keeping these mirrors give a lot of value anyways.
mboes
pushed a commit
to tweag/rules_haskell
that referenced
this issue
Mar 16, 2020
The mirrored protobuf archive from `https://mirror.bazel.build` now returns a 404. Given that mirror.bazel.build is undocumented thing that seems only used by internal google products and with no guaranty at all − see google-deepmind/lab#139 −, I don't think keeping these mirrors give a lot of value anyways.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, does bazel have any documentation about these "mirror builds"?
Is that a thing other bazel users can be expected to use?
Or since deepmind is a google thing, you are able to host things there?
just curious; thanks!
The text was updated successfully, but these errors were encountered: