| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Fixes #2067.
--
MOS_MIGRATED_REVID=138762258
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138757881
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138700111
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138695951
|
|
|
|
|
|
|
| |
at most K unique things at once.
--
MOS_MIGRATED_REVID=138684040
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138680612
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138669967
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138625702
|
|
|
|
|
|
|
|
|
|
|
| |
extra-actions for actions registered by Aspects injected by a top-level rule.
Because we can't know whether an aspect was injected by a top-level target or one of its children, we approximate it by only reporting extra-actions from Aspects that the top-level target could have injected.
RELNOTES: When --experimental_extra_action_top_level_only, Bazel reports extra-actions for actions registered by Aspects injected by a top-level rule (approximately).
--
MOS_MIGRATED_REVID=138570606
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138556910
|
|
|
|
|
|
|
| |
the scope and the parser prefix, both of which are final, it never changes.
--
MOS_MIGRATED_REVID=138536185
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138534021
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks several tests under //devtools/ide/eclipse/aspects as shown by the nightly []:
[]
*** Original change description ***
Restrict google_glob_information to eclipse_aspect.
'--legacy_expose_globs' flag has no effect now.
--
MOS_MIGRATED_REVID=138517258
|
|
|
|
|
|
|
| |
--
Change-Id: I908020889a0c573af401d67e988c41d33c654015
Reviewed-on: https://bazel-review.googlesource.com/#/c/7223
MOS_MIGRATED_REVID=138508319
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now flag_group can be marked with iterate_over field, that denotes for which
sequence variable the flag_group will be expanded repeatedly. This cl does that
in backwards compatible way as before, the iteration happened implicitly when the
used variable was found to be sequence at runtime. Because of that it adds some
extra code that will be removed once all the crosstools are migrated to the
explicit iteration.
--
MOS_MIGRATED_REVID=138501033
|
|
|
|
|
|
|
|
| |
- --client_debug that turns out debug logging from the client
- --connect_timeout_secs that controls the timeout of the initial Ping() RPC from the client to the server
--
MOS_MIGRATED_REVID=138491791
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use proto_lang_toolchain() in java_proto_library, after fixing breakage.
Verified on Jenkins, http://ci.bazel.io/job/Gerrit-bazel-tests/169/
*** Original change description ***
Automated [] rollback of commit a396b070ae36032a973672e11145533621c39edc.
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138432193
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138417384
|
|
|
|
|
|
|
| |
'--legacy_expose_globs' flag has no effect now.
--
MOS_MIGRATED_REVID=138410651
|
|
|
|
|
|
|
|
|
|
|
| |
recommended if there are no object files", when versioned shared library is in srcs fields like "a.so.2.0".
In appearsToHaveObjectFiles(), we take into account SHARED_LIBRARY, but no VERSIONED_SHARED_LIBRARY.
Fixes #310 .
--
MOS_MIGRATED_REVID=138408789
|
|
|
|
|
|
|
| |
RELNOTES: Comparing sets (`if set1 < set2:`) is not allowed anymore in Skylark because it didn't work correctly anyway.
--
MOS_MIGRATED_REVID=138408411
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138391269
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138387292
|
|
|
|
|
|
|
|
| |
away -- Bazel should still work with remote execution servers that don't have
that optimization.
--
MOS_MIGRATED_REVID=138384785
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For SpawnActions, depending on the value of use_default_shell_env,
the specified environment is taken. The shell environment, however,
consists of two parts: a static mapping of variables to values, and
a set of variables where the value is to be taken from the client
environment. Make sure, both parts are set correctly. Fixes #2035.
--
Change-Id: I32253e9bf651b18ca25107edc5fc839813905726
Reviewed-on: https://bazel-review.googlesource.com/#/c/7211
MOS_MIGRATED_REVID=138376914
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138372522
|
|
|
|
|
|
|
|
|
|
|
| |
context should generate a module map and module.
This whole code is a bit convoluted and the increasing number of boolean
parameters to initializeCppCompilationContext is smelly. I plan to clean this
up in a follow-up CL.
--
MOS_MIGRATED_REVID=138286169
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138231767
|
|
|
|
|
|
|
|
|
| |
documentation.
Fixes #1877.
--
MOS_MIGRATED_REVID=138199724
|
|
|
|
|
|
|
|
|
| |
This was an oversight on my part in the original implementation. As one
example, the Firebase AAR libraries contain AndroidManifest.xml's
with ${applicationId} and Google Play Services contain <meta-data> tags.
--
MOS_MIGRATED_REVID=138198047
|
|
|
|
|
|
|
| |
Add doc for the "read only" error message.
--
MOS_MIGRATED_REVID=138194709
|
|
|
|
|
|
|
| |
RELNOTES: Do not propagate aspect to its own attributes when using '*'.
--
MOS_MIGRATED_REVID=138194456
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change updates WindowsFileSystem so it:
- retrieves the DosFileAttributes instead of the
BasicFileAttributes, because the latter does not
report junctions as directories
- uses just isJunction to decide if a file is a
symlink, doesn't look at whether it's a
directory (again because java.nio.File also
incorrectly reports junctions as
non-directories)
Fixes https://github.com/bazelbuild/bazel/issues/1850
--
MOS_MIGRATED_REVID=138187220
|
|
|
|
|
|
|
| |
CompilationSupport.
--
MOS_MIGRATED_REVID=138185198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138182982
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138180229
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138161512
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138143803
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138112581
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Firebase Android libraries contain lots of AARs with manifests that include
${applicationId}. As far as I can tell, tools/android/merge_manifests.py only
allows for substitution of ${packageName} and not arbitrary placeholder
substitution. The new aar_import rule exposes the AARs in <sdk>/extras which
include include the Firebase Android libraries.
RELNOTES: Default android_manifest_merger is now "android" which uses the official Android manifest merger. http://tools.android.com/tech-docs/new-build-system/user-guide/manifest-merger
--
MOS_MIGRATED_REVID=138109902
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138104417
|
|
|
|
|
|
|
|
|
|
|
|
| |
blacklist.
This is intead of taking an attribute name and reading it inside of the class.
Motivation: using proto_lang_toolchain() rules means there's no longer an attribute that points at the blacklist.
Instead, we have an attribute that points at the toolchain, which itself points at the blacklist.
--
MOS_MIGRATED_REVID=138096096
|
|
|
|
|
|
|
| |
map, to emphasize that order matters.
--
MOS_MIGRATED_REVID=138090273
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
delimited).
Adds --experimental_build_event_binary_file option that enables varint delimited proto loggging to the specified file path
Adds varint delimited BuildEventStreamTransport and BuildEventStreamerModule
Adds BuildEventStreamerModule for configuring and setting up BuildEventStreamer and its associated BuildEventTransports.
Adds BuildEventTransportFactory which creates a Set of transports from command options.
Moves BuildEventStreamer configuration from BlazeCommandDispatcher and BuildEventStreamerModule
--
Change-Id: If71f2b58654879c2509206da47e6d1a846bf397f
Reviewed-on: https://bazel-review.googlesource.com/#/c/7010/
MOS_MIGRATED_REVID=138073726
|
|
|
|
|
|
|
| |
GITHUB: #1752
--
MOS_MIGRATED_REVID=138072464
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138039276
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138005602
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138004628
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When rewriting stable-status.txt, which happens on each build, avoid updating
the file's ctime and mtime if the new contents match what is already in the
file.
This prevents tickling the TimestampGranularityMonitor for what should be a
no-op update, which in turn could cause null/incremental builds to stall for
up to a second. The problem was magnified on macOS where the default HFS+
file system only has second-level granularity. (This also affects Linux, but
because current Linux file systems have milli/nanosecond-level granularity,
the wait imposed by TimestampGranularityMonitor is minimal and thus not
generally noticeable.)
--
MOS_MIGRATED_REVID=137983794
|
|
|
|
|
|
|
|
|
|
|
| |
instantiation of HttpDownloader and RepositoryCache in BazelRepositoryModule.
There are sufficient similarities between the download flows of HttpDownloader and MavenDownloader such that we can extend HttpDownloader to MavenDownloader, and reuse method headers such as checkCache and download.
GITHUB: #1752
--
MOS_MIGRATED_REVID=137982375
|