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

	Commit message (Collapse)	Author	Age
*	Refactoring: makes the code simpler by deleting Metadata and InputArtifactData.	shahan	2018-06-06
\| \| \| \| \| \|	(minor) ActionFS now implements MetadataProvider.getInput PiperOrigin-RevId: 199575194
*	Clean up code that directly imports nested classes like Builder, Entry, etc.	jcater	2018-05-02
\| \| \| \|	PiperOrigin-RevId: 195100670
*	Move FileStateValue.Type to Metadata; add Metadata.getType()	ulfjack	2017-12-21
\| \| \| \| \| \| \| \|	This is in preparation for merging FileArtifactValue and FileStateValue. Progress on #3360. PiperOrigin-RevId: 179832948
*	Replace all usages of Blaze's Preconditions class with guava.	tomlu	2017-11-09
\| \| \| \| \| \| \| \|	Blaze had its own class to avoid GC from varargs array creation for the precondition happy path. Guava now (mostly) implements these, making it unnecessary to maintain our own. This change was almost entirely automated by search-and-replace. A few BUILD files needed fixing up since I removed an export of preconditions from lib:util, which was all done by add_deps. There was one incorrect usage of Preconditions that was caught by error prone (which checks Guava's version of Preconditions) that I had to change manually. PiperOrigin-RevId: 175033526
*	Fix NPE in WorkerFilesHash.	philwo	2017-08-29
\| \| \| \| \| \| \| \|	We must check that a given artifact is a file, before calling getDigest, according to the interface contract specified in actions/Metadata.java. Add a regression test to bazel_worker_test.sh, too. It's enough to simply add a directory entry to the worker's data to trigger the original bug. PiperOrigin-RevId: 166856512
*	When a worker can no longer be used, because one or more of its files on ↵	philwo	2017-08-17
\| \| \| \| \| \| \|	disk have changed since it was launched, print which files have changed. RELNOTES: Improved logging when workers have to be restarted due to its files having changed. PiperOrigin-RevId: 165419664
*	Refactor persistent workers to use SpawnRunner.	Benjamin Peterson	2017-08-11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Change the persistent worker spawn strategy to extend AbstractSpawnStrategy and put the actual logic into WorkerSpawnRunner. WorkerTestStrategy is unaffected. I had to extend SpawnPolicy with a speculating() method. Persistent workers need to know if speculation is happening in order to require sandboxing. Additionally, I added java_test rules for the local runner tests and worker tests. See https://github.com/bazelbuild/bazel/issues/3481. NOTE: ulfjack@ made some changes to this change before merging: - changed Reporter to EventHandler; added TODO about its usage - reverted non-semantic indentation change in AbstractSpawnStrategy - reverted a non-semantic indentation change in WorkerSpawnRunner - updated some internal classes to match - removed catch IOException in WorkerSpawnRunner in some cases, removed verboseFailures flag from WorkerSpawnRunner, updated callers - disable some tests on Windows; we were previously not running them, now that we do, they fail :-( Change-Id: I207b3938f0dc84d374ab052d5030020886451d47 PiperOrigin-RevId: 164965398
*	Simplify the ActionInputFileCache	ulfjack	2017-07-06
\| \| \| \| \| \| \| \| \|	Add a single getMetadata method (matching MetadataHandler), and rewrite everything in those terms. This is in preparation for merging ActionInputFileCache and MetadataHandler. PiperOrigin-RevId: 161053535
*	Initial code for Persistent Java Test Runner.	Kush Chakraborty	2016-12-09
	At this point this does nothing more than re-run the exact same test without having to re-start the test runner. In future iterations the aim is to be able to re-run tests with modified code, without having to re-start the test runner. To test out the WorkerTestStrategy simply use --test_strategy=experimental_worker for a test with bazel. -- PiperOrigin-RevId: 141465929 MOS_MIGRATED_REVID=141465929