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

	Commit message (Collapse)	Author	Age
*	Expose an actions provider on RuleConfiguredTarget instances.	cparsons	2018-03-06
\| \| \| \| \| \| \| \| \|	Given a target (for example from a skylark aspect), one will be able to access a list of actions that the target generated using "target.actions". This is without additional memory footprint. Actions themselves are not fully exposed to skylark (and thus there isn't much meaning to gather from them in skylark yet). Access methods will follow soon. RELNOTES: None. PiperOrigin-RevId: 188098079
*	MockRule-ify some more tests.	gregce	2017-11-29
\| \| \| \|	PiperOrigin-RevId: 177339358
*	Only load the whitelist for Android targets if they use feature flags.	mstaib	2017-09-21
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Currently, every Android-related top-level target will use the feature flag whitelist, regardless of whether it has any feature flags. This change makes it so that these targets only load the whitelist if they need it. In the process, it moves the value of the whitelist from the attribute definition method to outside of it. Because it's a builder, this is only a minor change to each callsite. RELNOTES: None. PiperOrigin-RevId: 169405621
*	CI,windows: create test_suites for Windows tests	L?szl? Csomor	2017-09-19
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Add recursive test_suite rules for all tests that ci.bazel.io runs for Windows, and set the top-level test_suite as the CI test target. Doing so shortens the command line and works around https://github.com/bazelbuild/bazel/issues/3742 I verified that the old set of tests are the same as the new set. Change-Id: Id8d5da3f0c03c9b8969a9f8e1e9a3096888365aa PiperOrigin-RevId: 169242858
*	More BUILD file refactorings.	philwo	2017-09-06
\| \| \| \| \| \| \| \| \|	Split collect, concurrent, vfs, windows into package-level BUILD files. Move clock classes out of "util", into their own Java package. Move CompactHashSet into its own Java package to break a dependency cycle. Give nestedset and inmemoryfs their own package-level BUILD files. PiperOrigin-RevId: 167702127
*	Move RuleConfiguredTargetFactory to lib.analysis	ulfjack	2017-08-07
\| \| \| \| \| \| \|	This is part of splitting up the build-base library into separate libraries for analysis, exec, and rules. PiperOrigin-RevId: 164446955
*	Add missing test dependency to unbreak the build	Jakob Buchgraber	2017-07-27
\| \| \| \| \| \| \|	Introduced by b344e2c5a97b0eeacb796db20bb894f21283d358 Change-Id: I942b63cd52520a37e5bf2c7b04f3eed1615ec71e PiperOrigin-RevId: 163323682
*	Package whitelisting: New implementation for feature whitelisting	plf	2017-07-26
	This builds on top of mstaib's idea to use package groups to whitelist projects which can use certain features in the analysis phase. Instead of using configurations and a flag, this way of implementing whitelists requires using two helper methods, one that adds an implicit attribute to every rule that has functionality that must be whitelisted and a different method to check whether a given package is whitelisted to use that feature. RELNOTES:none PiperOrigin-RevId: 163200890