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

	Commit message (Collapse)	Author	Age
*	Filter middleman artifacts from NamedArtifactGroup	ulfjack	2018-06-08
\| \| \| \|	PiperOrigin-RevId: 199786555
*	Rename BuildEventConverters to BuildEventContext	ulfjack	2018-05-17
\| \| \| \| \| \| \|	This is in preparation for adding options to the class, which can be used to modify the behavior of build events posted to the BEP. PiperOrigin-RevId: 196997573
*	Implement a limit for named_set_of_file events	ulfjack	2018-05-15
\| \| \| \| \| \| \| \| \| \| \|	This adds a command-line option which can be used to force Bazel to split up very large events, e.g., events with hundreds of thousands of entries. This is rare, but happens occasionally. It would be better to control the maximum event size directly, but that is significantly more difficult to do here. PiperOrigin-RevId: 196690600
*	Simplify root relative path calculation.	tomlu	2018-01-12
\| \| \| \| \| \|	This is a first-class artifact concept. No need to go the long way to get this path. PiperOrigin-RevId: 181717016
*	BEP: use full relative path as file name	Klaus Aehlig	2017-06-09
\| \| \| \| \| \| \| \|	The base names are not necessarily unique enough to identify which artifact is being talked about. Change-Id: Ic8ff78c8f26f98e0e9a2d558d03f4cf9ae9111c8 PiperOrigin-RevId: 158499210
*	BEP: Extend infrastructure to allow reporting artifacts only once	Klaus Aehlig	2017-04-07
	Extend the functionality of the BuildEventStreamer to report those parts of NestedSets of Artifacts not reported earlier. In this way, duplicate reporting can be avoided, without the events themselves having to know which artifacts are known already. Change-Id: Ia959c28c440301860eac57ea5d9a712c0d49ebdf PiperOrigin-RevId: 152497672