| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Turns out --symlink_prefix is not applied to the bazel-{out,workspace}
unlike bazel-{bin,genfiles,testlogs} thus breaking the semantics of
--symlink_prefix.
This CL fixes the problem by using the symlink prefix instead of the
product name when building the output and exec root symlinks.
RELNOTES[INC]: Using --symlink_prefix is now applied to the output
symlink (e.g. bazel-out) and the exec root symlink (e.g. bazel-workspace).
--
PiperOrigin-RevId: 146902534
MOS_MIGRATED_REVID=146902534
|
|
|
|
|
|
|
|
|
|
|
| |
This confused me every time I looked it up. Thought that was working through some magic shell alias tricks until I found the files on my hard drive.
Closes #2203.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2203
PiperOrigin-RevId: 141556677
MOS_MIGRATED_REVID=141556677
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=139180153
|
|
|
|
|
|
|
|
|
| |
#getShellExecutable() method.
That's all it was used for anyway.
--
MOS_MIGRATED_REVID=133824769
|
|
|
|
|
|
|
| |
on Windows by default)
--
MOS_MIGRATED_REVID=129319018
|
|
|
|
|
|
|
|
|
| |
Now we can use 'bazel run' to run cpp and java binary!
--
Change-Id: I84b597765dc77127f3fb701d7bd4a81f6dc44660
Reviewed-on: https://bazel-review.googlesource.com/#/c/4054
MOS_MIGRATED_REVID=127834930
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Apparently we now try to open output files for the process twice: once when we are constructing the output streams, and the second time when we tell the process to redirect its outputs. This causes the outputs to be empty on Windows
*** Original change description ***
Do redirection of stdout / stderr in Java instead of reimplementing it in every process wrapper again.
--
MOS_MIGRATED_REVID=126801016
|
|
|
|
|
|
|
| |
every process wrapper again.
--
MOS_MIGRATED_REVID=126279021
|
|
|
|
|
|
|
|
|
| |
BlazeRuntime#getProductName() or a reference to TestConstants.PRODUCT_NAME for tests.
This CL prepares the codebase in order to delete the constant.
--
MOS_MIGRATED_REVID=122993568
|
|
|
|
|
|
|
| |
Fixes #1290.
--
MOS_MIGRATED_REVID=122726071
|
|
|
|
|
|
|
|
|
|
|
|
| |
With remote repositories, it is useful to do this to execute an input
file which isn't actually part of the source tree.
Closes #984
--
Change-Id: Ic986ea9bbe88e0edb933939ce1d7a8b6ea9d6e88
Reviewed-on: https://bazel-review.googlesource.com/#/c/3030/
MOS_MIGRATED_REVID=120248102
|
|
|
|
|
|
|
|
| |
As part of that, move a BinTools and the WorkspaceStatusActionFactory to the
BlazeWorkspace.
--
MOS_MIGRATED_REVID=119633702
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118561661
|
|
|
|
|
|
|
|
| |
This simplify the bootstrap process and remove a C++ tool from
the bootstrap binary.
--
MOS_MIGRATED_REVID=112394555
|
|
|
|
|
|
|
| |
Reduces garbage.
--
MOS_MIGRATED_REVID=109914243
|
|
|
|
|
|
|
| |
"bin"/"genfiles" instead of the default ones)
--
MOS_MIGRATED_REVID=108699595
|
|
|
|
|
|
|
| |
Preparation for running multiple commands in parallel.
--
MOS_MIGRATED_REVID=105840167
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103374106
|
|
|
|
|
|
|
|
| |
They are usually on the same line, so doing this in separate changes can cause
merge conflicts.
--
MOS_MIGRATED_REVID=103362797
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was persuing the idea that BuildView could become stateless. While that
should be possible, we're currently still relying on minimal state in
BuildView (from tests at least) in a way that makes it tricky to remove.
Instead, I'm now trying to move the BuildView into CommandEnvironment, and
create a new one as needed (only for build commands); that makes it safe in the
presence of concurrently running commands, as long as they don't use the same
BuildView instace. (Of course, allowing commands to run concurrently will need
more changes outside of BuildView.)
--
MOS_MIGRATED_REVID=103279370
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103269584
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103175472
|
|
|
|
|
|
|
|
| |
The very long term plan is to make BlazeRuntime immutable, so that we can
run multiple commands in the same server.
--
MOS_MIGRATED_REVID=103080946
|
|
|
|
|
|
|
|
|
| |
color when the build fails.
Includes fix for problems causing the original slowdown to blaze query
--
MOS_MIGRATED_REVID=99755414
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Query performance regression.
--
MOS_MIGRATED_REVID=99560234
|
|
|
|
|
|
|
| |
color when the build fails.
--
MOS_MIGRATED_REVID=98736813
|
|
|
|
|
|
|
|
|
|
| |
`bazel help completion` dump all options completion pattern
for each command, giving hints on the format of the completion
residue (e.g., `label`, `path`, `{a,enum}`, ...). This
dump can be used to generate completion scripts.
--
MOS_MIGRATED_REVID=90743024
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87728012
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87513766
|
|
|
|
|
|
|
| |
can be used in their stead.
--
MOS_MIGRATED_REVID=87334648
|
|
--
MOE_MIGRATED_REVID=85702957
|