Bazel – Correct, reproducible, fast builds for everyone

Re:Bazel – Correct, reproducible, fast builds for everyone by dpark on Wednesday March 25, 2015 @12:35PM (#9264057)

No, it's something that Perforce allows (because it scales sufficiently). It has nothing to do with C++.

You can impose order within the monolithic repo by partitioning projects into their own branches or directories and only pulling down the necessary pieces.

Whether this is better than a bunch of small repos is debateable.

[ Parent | on HN ]

Re:Bazel – Correct, reproducible, fast builds for everyone by nevir on Wednesday March 25, 2015 @01:46PM (#9264561)

Perforce (the product) doesn't really scale sufficiently for the Googles/Amazons/Microsofts of the world, sadly.

I think they've all moved to custom forks/implementations due to the insane SPOF that Perforce servers are (and their hardware requirements). But up til that point, heck yeah!

[ Parent | on HN ]

Re:Bazel – Correct, reproducible, fast builds for everyone by dpark on Wednesday March 25, 2015 @05:50PM (#9266195)

Well, Perforce in its default state may not scale sufficiently, but at least two of the companies on that list have managed to make it work (presumably with a lot of investment, though). :)

I didn't know Amazon was using Perforce. I interviewed someone from Amazon recently and he indicated they were on Git for most things now.

[ Parent | on HN ]

Re:Bazel – Correct, reproducible, fast builds for everyone by gagomes on Thursday March 26, 2015 @12:11AM (#9267778)

Amazon has phased out perforce a year ago. There is very little left, most repositories (perforce, svn, etc) were migrated to git repositories.

[ Parent | on HN ]