bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Refactor the FileSystem API to allow for different hash functions.	buchgr	2017-11-30
\| \| \| \| \| \| \| \| \| \| \| \| \|	Refactor the FileSystem class to include the hash function as an instance field. This allows us to have a different hash function per FileSystem and removes technical debt, as currently that's somewhat accomplished by a horrible hack that has a static method to set the hash function for all FileSystem instances. The FileSystem's default hash function remains MD5. RELNOTES: None PiperOrigin-RevId: 177479772
*	remote: Chunker.reset() should release resources.	buchgr	2017-07-17
\| \| \| \| \|	RELNOTES: None. PiperOrigin-RevId: 161970540
*	remote: Rewrite Chunker	buchgr	2017-07-12
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	- Remove the Chunker.Builder and use the Chunker constructors instead. - Fix a correctness bug, where the chunker would ignore the return value of InputStream.read(byte[]). - Have Chunk.getData() return a ByteString as opposed to a byte[]. All callsides need ByteString objects and this change makes the subsequent change possible. - Have the Chunker use a preallocated byte[] in order to avoid allocating a new one on every call to next(). RELNOTES: None. PiperOrigin-RevId: 161637158
*	Switching Bazel to use the new remote execution API: ↵	olaola	2017-06-09
\| \| \| \| \| \| \| \| \|	https://docs.google.com/document/d/1AaGk7fOPByEvpAbqeXIyE8HX_A3_axxNnvroblTZ_6s/edit Also refactored away the various Interface files, no need since unit testing can be done with mocking the appropriate gRPC Impl classes directly (see tests). This also fixes the RemoteSpawnRunner, which should use different objects for remote caching and remote execution, the same way RemoteSpawnStrategy does. RELNOTES: n/a PiperOrigin-RevId: 158473700
*	Refactoring the chunking logic out of GrpcActionCache, and cleaning it up. Also	olaola	2017-04-06
\| \| \| \| \| \| \| \| \| \| \| \|	added tests. This should not conflict with any of Ulf's upcoming CLs. I need it in preparation for the next CL, which fixes the bug that I don't limit the message size according to grpcChunkSizeBytes and don't do chunking in RemoteWorker.java, causing it to fail on uploading large outputs. TESTED=unit / integration tests RELNOTES: n/a PiperOrigin-RevId: 152385956
*	Automated g4 rollback of commit 520f947580634cb9b62020fba4c93d5e78044ccf.	mstaib	2017-04-06
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Reason for rollback * Broke mac_jdk7_test. * Original change description * Refactoring the chunking logic out of GrpcActionCache, and cleaning it up. Also added tests. This should not conflict with any of Ulf's upcoming CLs. I need it in preparation for the next CL, which fixes the bug that I don't limit the message size according to grpcChunkSizeBytes and don't do chunking in RemoteWorker.java, causing it to fail on uploading large outputs. TESTED=unit / integration tests RELNOTES: n/a PiperOrigin-RevId: 152270056
*	Refactoring the chunking logic out of GrpcActionCache, and cleaning it up. Also	olaola	2017-04-06
	added tests. This should not conflict with any of Ulf's upcoming CLs. I need it in preparation for the next CL, which fixes the bug that I don't limit the message size according to grpcChunkSizeBytes and don't do chunking in RemoteWorker.java, causing it to fail on uploading large outputs. TESTED=unit / integration tests RELNOTES: n/a PiperOrigin-RevId: 152258232