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

	Commit message (Collapse)	Author	Age
*	Batch all DependencyResolver#getTarget calls. This leads to some duplicate ↵	janakr	2018-08-09
\| \| \| \| \| \|	iteration, but that should be cheap, while requesting packages sequentially can hurt... PiperOrigin-RevId: 208126130
*	Rename the implicit attribute used to store toolchain dependencies.	jcater	2018-06-21
\| \| \| \|	PiperOrigin-RevId: 201565941
*	Refactor root cause reporting in ConfiguredTargetFunction	ulfjack	2018-05-29
\| \| \| \| \| \|	We now track Causes instead of plain Labels, which will allow us to do better reporting in the future. Add basic tests. PiperOrigin-RevId: 198380468
*	Unfork SplitTransition / PatchTransition invocations.	gregce	2018-05-24
\| \| \| \| \| \|	Part of https://docs.google.com/document/d/1_UJKmAQ9EE8i3Pl0il3YLTYr-Q9EKYYyLatt2zohfyM/edit# PiperOrigin-RevId: 197890685
*	Rename PatchTransition.apply to PatchTransiton.patch.	gregce	2018-05-23
\| \| \| \| \| \| \|	This unclashes with the incoming ConfigurationTransition.apply method described in https://docs.google.com/document/d/1_UJKmAQ9EE8i3Pl0il3YLTYr-Q9EKYYyLatt2zohfyM/edit#heading=h.96gongkwg852. PiperOrigin-RevId: 197769784
*	Add the capability to register a trimming RuleTransitionFactory.	mstaib	2018-04-19
\| \| \| \| \| \| \| \| \| \|	This RuleTransitionFactory will be applied to all targets after other transitions, and is intended to be used to manually trim the configuration based on tagging of that target. This is a stopgap feature until automatic trimming of configuration can be implemented. RELNOTES: None. PiperOrigin-RevId: 193573013
*	Create a new proto output formatter for cquery. Also add flag ↵	juliexxia	2018-04-11
\| \| \| \| \| \|	--[no]proto:include_configurations which when used, makes cquery proto output appear exactly like query proto output so tools that are already using this can seamlessly transition. PiperOrigin-RevId: 192470626
*	Error out gracefully instead of crashing blaze when --output=transitions is ↵	juliexxia	2018-04-05
\| \| \| \| \| \|	used without the --transitions flag PiperOrigin-RevId: 191755762
*	Put configuration checksum into BuildOptions$OptionsDiffForReconstruction ↵	janakr	2018-03-28
\| \| \| \| \| \| \| \|	and make it available to ConfiguredTarget. Also give BuildConfigurationValue.Key the same toString() that BuildConfiguration had, so we recover how we used to print out ConfiguredTarget labels in debugging. This may have a tiny bit of overhead in serialization, but we'll cross that bridge when we come to it. Could just make the string a constant. PiperOrigin-RevId: 190787145
*	Get rid of call to deprecated ConfiguredTarget.getConfiguration()	juliexxia	2018-03-28
\| \| \| \|	PiperOrigin-RevId: 190777533
*	Move the default cquery output format to its own callback and standardize ↵	juliexxia	2018-03-27
\| \| \| \| \| \|	cquery output callback logic PiperOrigin-RevId: 190667120
*	Get rid of some more #getConfiguration calls.	janakr	2018-03-26
\| \| \| \|	PiperOrigin-RevId: 190502786
*	Create a new output formatter for cquery which output transition information ↵	juliexxia	2018-03-23
	in either a FULL or LITE version. Trigger new output with the new --transitions cquery flag in the new CqueryOptions class. PiperOrigin-RevId: 190278664