| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
RELNOTES[INC]: The --cwarn command line option is not supported anymore. Use --copt instead.
--
MOS_MIGRATED_REVID=123101536
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top, and finishes replacing them with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}.
RELNOTES: Replace --java_langtools, --javabuilder_top, --singlejar_top,
--genclass_top, and --ijar_top with
java_toolchain.{javac,javabuilder,singlejar,genclass,ijar}
--
MOS_MIGRATED_REVID=120154954
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a less specific option specification in a rc file could override a more specific option specification when there's a non-trivial Command hierarchy. A concrete example would be a "build --foo=1" line overriding a "test --foo=2" line for a "test" invocation.
See the added test for more details.
Also fix some typos in BlazeCommandDispatcherRcoptionsTest.java.
Note that commit dc0fbb42ab22ab8f3205b0884069e1ffe03677c9 was rolled back in commit 417dad0f1e0d0ed4ccd5f8e52b49eb79937da49d which also incidentally rolled back commit 4f0fbe1b09333806cce76b75214e98c7684766e0. So this change is effectively a roll-forward of both of those, plus the bug fix, plus the typo fixes, and plus a documentation update.
--
MOS_MIGRATED_REVID=119276218
|
|
|
|
|
|
|
|
|
|
| |
Specially because base_workspace is not involved anymore
since the 0.2.0 release.
--
Change-Id: I70143a57202f6d487f7ab828da61f0ea127694e8
Reviewed-on: https://bazel-review.googlesource.com/c/3130/
MOS_MIGRATED_REVID=118036928
|
|
|
|
|
|
|
| |
Fixes #995.
--
MOS_MIGRATED_REVID=116247058
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=115320148
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Issue that caused the rollback (#819) is resolved
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //......
--
MOS_MIGRATED_REVID=113259357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=113164089
|
|
|
|
|
|
|
|
|
|
|
|
| |
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=112604261
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112573386
|
|
|
|
|
|
|
| |
Fixes #790
--
MOS_MIGRATED_REVID=112563137
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112231484
|
|
|
|
|
|
|
|
|
| |
threads!
Fixes #748
--
MOS_MIGRATED_REVID=111468883
|
|
|
|
|
|
|
| |
to aid in diagnosing issue #748.
--
MOS_MIGRATED_REVID=111360258
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109881691
|
|
|
|
|
|
|
|
|
|
| |
- Add mitigation of the common problem to the documentation
- Add indication on how to activate sandboxing on some machine (GKE nodes for example)
Fixes #433
--
MOS_MIGRATED_REVID=109879921
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In particular:
- Separate the implementation of maven_server into a RepositoryFunction and one that creates the MavenServerValue (ideally, maven_server wouldn't exist but we'll have to make to for the time being)
- Refactor the logic of determining whether an external repository needs to be re-fetched to RepositoryDelegatorFunction
- Make RepositoryFunctions not be SkyFunctions anymore (they are called from RepositoryDelegatorFunction, though, who *is* a SkyFunction)
- Add a Skyframe dirtiness checker that makes --nofetch RepositoryValues not be cached
- Add a bunch of test cases and javadoc
There is only one wart that I know of that remains: changes to BUILD files of new_* repository rules that weren't refetched when their RepositoryValue was initiall created on server restart won't take effect. This is because we don't add those BUILD files to the created RepositoryValue. This will fix itself once the ExternalFilesHelper refactoring is submitted.
--
MOS_MIGRATED_REVID=109768345
|
|
|
|
|
|
|
| |
target patterns and are thus neither built nor tested by invocations like "blaze test //my/project/..."
--
MOS_MIGRATED_REVID=109251573
|
|
|
|
|
|
|
|
|
| |
target pattern.
Apart from the tests, I also tested this manually running "bazel query //..." in a tree with convenience symlinks.
--
MOS_MIGRATED_REVID=108325454
|
|
|
|
|
|
|
|
|
|
| |
I filed #546 because I didn't notice --host_crosstool_top does what I
want.
--
Change-Id: Ib219753ad69c3026f1aa6d1889a0e7fac4449b2b
Reviewed-on: https://bazel-review.googlesource.com/#/c/2261/
MOS_MIGRATED_REVID=108267036
|
|
|
|
|
|
|
| |
Also, fix said documentation.
--
MOS_MIGRATED_REVID=108247791
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108145081
|
|
|
|
|
|
|
|
|
| |
through to the JVM instead of (almost certainly incorrectly) splitting the options along spaces.
This allows us to pass non-quote-delimited strings to the JVM, which is necessary for things like -XX:OnOutOfMemoryError="kill -3 %p" (normally bash strips those quotes, but they're not stripped when passed via --host_jvm_args).
--
MOS_MIGRATED_REVID=107820087
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN" will *not* be traversed for transitive target patterns. The motivation here is to allow directories that intentionally contain wonky symlinks (e.g. foo/bar -> foo) to opt out of being consumed by Blaze. For example, given
<workspace>/foo
bar
bad -> .
DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
the 'bad' symlink will *not* be traversed by the pattern '//foo/...'.
--
MOS_MIGRATED_REVID=107738930
|
|
|
|
|
|
|
| |
Fixes #529
--
MOS_MIGRATED_REVID=106883457
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
previous commit
Document and test how rules can run without the sandbox.
The only documentation about usable tags values was in a weird place,
along with duplicated information about flaky tests.
--
Change-Id: Ib98a0a5c582890512161ecf9f5d89c8e78d9ad68
Reviewed-on: https://bazel-review.googlesource.com/#/c/2220
MOS_MIGRATED_REVID=106858070
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106092764
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105952522
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104958733
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104644891
|
|
|
|
|
|
|
| |
Fixes #134.
--
MOS_MIGRATED_REVID=103935102
|
|
|
|
|
|
|
| |
I promised to add this example after responding to a user question in the bazel irc.
--
MOS_MIGRATED_REVID=102120516
|
|
|
|
|
|
|
| |
given
--
MOS_MIGRATED_REVID=102046602
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
documentation. Replaces instances of "build root" with "workspace directory"
as appropriate.
Makes the following changes:
- /docs/build-ref.html: Adds definition of workspace
- /docs/external.md: Replaces "build root" terminology with "workspace"
- /docs/getting-started.md: Adds link to workspace definition
- /docs/bazel-user-manual.html: Adds link to workspace definition
--
MOS_MIGRATED_REVID=101885966
|
|
|
|
|
|
|
| |
my best day today.
--
MOS_MIGRATED_REVID=101557371
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101555906
|
|
|
|
|
|
|
| |
strategy is only used if your Linux kernel is new enough and your running system supports it. If this breaks you, please file a bug and you can always go back to non-sandboxed execution by using --spawn_strategy=standalone.
--
MOS_MIGRATED_REVID=101464269
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100315352
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100303875
|
|
|
|
|
|
|
| |
RELNOTES: nope
--
MOS_MIGRATED_REVID=99931043
|
|
|
|
|
|
|
| |
Rollback of commit b961bb931400044ed91e6b0b596f94fe983f9f17.
--
MOS_MIGRATED_REVID=98833728
|
|
|
|
|
|
|
| |
Fixes #309.
--
MOS_MIGRATED_REVID=98639996
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98393704
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks LIPO, []
*** Original change description ***
Blaze changes to support LLVM profile feedback.
--
MOS_MIGRATED_REVID=98382087
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97610963
|
|
|
|
|
|
|
| |
The alternative is too horrifying to consider.
--
MOS_MIGRATED_REVID=97398060
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96911530
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96814231
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96802902
|
|
|
|
|
|
|
| |
exist and hasn't existed for a while.
--
MOS_MIGRATED_REVID=96711367
|