The bintray is public as well and built to serve binaries. I'd definitely switch - no backup.
On Thu, Oct 23, 2014 at 3:21 PM, Joe Smith <yasumo...@gmail.com> wrote: > Thanks for the insight! This is going to be for the external Apache > codebase, so we're okay with using > https://pantsbuild.github.io/binaries/build-support if you're also using > it as a fallback. > > Thanks! > > On Thu, Oct 23, 2014 at 11:32 AM, Eric Ayers <zun...@squareup.com> wrote: > >> At Square we have some binaries that we override, so we have an internal >> site for those, and then we fall back to this URL for others. >> >> pants_support_baseurls = [ >> 'https://our-internal-machine/test-build-support', >> 'https://pantsbuild.github.io/binaries/build-support', >> ] >> >> We have a comment to find a better solution. I’m not sure keeping >> binaries in github is a great long term thing because I’m not sure it could >> handle a lot of traffic. >> >> On Thu, Oct 23, 2014 at 2:14 PM, Joe Smith <yasumo...@gmail.com> wrote: >> >> Hi all, >>> >>> Aurora ran into an issue where it could not build on OS X 10.10 >>> <https://issues.apache.org/jira/browse/AURORA-867>, and we didn't get >>> much clarity on the filed issue on github >>> <https://github.com/pantsbuild/pants/issues/690>. >>> >>> I've sent out a review for Aurora <https://reviews.apache.org/r/27066/> >>> to use https://pantsbuild.github.io/binaries/build-support- does that >>> sound reasonable? If that's going to be ~stable for the foreseeable future >>> then that'd be awesome, but I don't want to force a public artifact store >>> on you guys if that's not its purpose. >>> >>> Thanks! >>> Joe >>> >> >> > >
