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

	Commit message (Collapse)	Author	Age
*	Skylark repos: for failed patch command, also report stdout	Klaus Aehlig	2018-06-13
\| \| \| \| \| \| \| \| \| \|	The patch(1) utility usually gives error messages on stdout. So it is not useful to report only stderr in case a patch failed. Report both. Fixes #5379. Change-Id: Ief198849e29ca989dfdefe2fadf495a0b0949972 PiperOrigin-RevId: 200377306
*	Skylark repositories: support additional arguments for the patch tool	Klaus Aehlig	2018-06-13
\| \| \| \| \| \| \| \| \| \| \| \|	Instead of hard-coding "-p0", allow the arguments for that patch tool to be overridden. In particular, this supports the use case of patches generated with `git format-patch` which are to be read as `-p1`. Improves on #5379. Closes #4974 as superseded. Change-Id: I809fde14beab21d8a755ba4f1706b602bae3c1bb PiperOrigin-RevId: 200373909
*	Support patching of git repositories as well	Klaus Aehlig	2018-03-01
\| \| \| \| \| \| \| \| \| \|	By simply sharing the utility function. In this way, we get feature parity between git_repository and http_archive. Fixes #4676. Change-Id: I99b300e42b2f267d8d04fd965f09c24f3ae54f10 PiperOrigin-RevId: 187450644
*	external_patch_test: set user name/email	Klaus Aehlig	2018-02-28
\| \| \| \| \| \| \| \|	...for git does not allow generating a commit otherwise, at least some versions. Change-Id: Id584999816ecff6954118811e4f753e618b50194 PiperOrigin-RevId: 187316142
*	external repos: add a Skylark library for common tasks	Klaus Aehlig	2018-02-28
\| \| \| \| \| \| \| \|	...thus avoiding having them several times for the various repository rules, each with slightly different behavior and bugs. Change-Id: I6cec0c0dd0901453458903e226ceb2098a93cdd8 PiperOrigin-RevId: 187306904
*	http_archive: allow top-level BUILD files to be overridden	Klaus Aehlig	2018-02-01
\| \| \| \| \| \| \| \| \|	..by the `build_file` parameter, even if the external repository contains a top-level BUILD file. While there, also add a test verifying that this is also possible via the `build_file_content`. Change-Id: I1b875c147cfcd6f1c70b8efeb10c2b406eeacf6a PiperOrigin-RevId: 184134041
*	http_archive: test patch files are tracked	Klaus Aehlig	2018-01-17
\| \| \| \| \| \| \| \| \| \|	Add a test verifying that changes to the patch file trigger a a rebuild of the external repository. Ensures soundness of the fix for Issue #3395. Change-Id: Ida3823b7cddbe3bb54f0f0e24074e3854055f6e1 PiperOrigin-RevId: 182226112
*	http_archive: support programmatic patching	Klaus Aehlig	2018-01-16
\| \| \| \| \| \| \| \| \| \| \|	Support applying a sequence of commands to an http_archive, after the patch files are applied. In this way, tasks like shebang-fixes can easily be added. Fixes #3395. Change-Id: Ifdad584a852efd425c436d57ef71a0d681488629 PiperOrigin-RevId: 182037265
*	Support patches in http_archive	Klaus Aehlig	2018-01-15
	Support applying a sequence of patches for external repositories imported via http_archive. (Note that we only support the version from @bazel_tools, not the deprecated native rules.) Works towards #3395. Change-Id: I96c746acc04790b051eb686856c04a3ff3c90059 PiperOrigin-RevId: 181975322