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

	Commit message (Collapse)	Author	Age
*	Accept Durations in the CriticalPathComponent and Profiler.	ccalvarin	2018-02-22
\| \| \| \| \|	RELNOTES: None. PiperOrigin-RevId: 186658512
*	Add ActionKeyContext to Action#getKey.	tomlu	2017-11-29
\| \| \| \| \| \| \|	This key context can be used by actions to share partial key computations, for instance when computing MD5s for nested sets. RELNOTES: None PiperOrigin-RevId: 177359607
*	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
*	When tracking the critical path, if not keeping incremental state, don't ↵	janakr	2017-04-06
\| \| \| \| \| \| \| \|	keep references to actions indefinitely. Instead, once an action is finished executing, keep just some metadata about it. This allows actions to be unconditionally dropped when running with --batch, --discard_analysis_cache, and --keep_going, even if profiling is enabled. The additional fields here add between 8 and 12 bytes per component, and we have one component per action. This additional penalty is only incurred when we are already saving memory, so I think it's ok. The full penalty will be realized only towards the end of the build, when every action has started executing at least once. Users can still specify --noexperimental_enable_critical_path_profiling if they want to squeeze even more memory out. PiperOrigin-RevId: 152328870
*	Rationalize copyright headers	Damien Martin-Guillerez	2015-09-25
\| \| \| \| \| \| \| \| \| \| \|	The headers were modified with `find . -type f -exec 'sed' '-Ei' 's\|Copyright 201([45]) Google\|Copyright 201\1 The Bazel Authors\|' '{}' ';'` And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan. The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand. -- MOS_MIGRATED_REVID=103938715
*	Compute action start time in critical path using Clock.currentTimeMillis ↵	Miguel Alcon Pinto	2015-02-25
\| \| \| \| \| \| \|	instead of nanoTime. As nanoTime should only be used to compute time differences. To avoid having to pass two long values representing time (And calling twice to Clock.xxx methods per action executed) we compute the wall time by passing a clock and computing the difference from the start nano time. -- MOS_MIGRATED_REVID=87102963
*	Update from Google.	Han-Wen Nienhuys	2015-02-25
	-- MOE_MIGRATED_REVID=85702957