| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
to get the remote execution properties.
Fixes #4128.
Change-Id: I7e71caef2465204d2dd8225448d54e52366807e6
PiperOrigin-RevId: 179595126
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a generic java_toolchain.javacopts attribute, and make some attributes that
aren't needed for Java 9 optional (source_version, target_version, bootclasspath,
extclasspath). In hindsight there aren't any real advantages to baking details
of javac flags into java_toolchain except for the ones that deal with search paths
(classpath etc.). Using a more general javacopts attribute will avoid churn in the
future as the javac API changes.
This is pre-work for supporting e.g. --release.
PiperOrigin-RevId: 179590640
|
|
|
|
| |
PiperOrigin-RevId: 179588512
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179588174
|
|
|
|
|
|
| |
and replace the only use with java_common.default_javac_opts.
PiperOrigin-RevId: 179571481
|
|
|
|
|
|
|
|
|
|
|
|
| |
instrumentation android_binary's AndroidManifest.xml references the correct package name of the instrumented android_binary.
During an instrumentation test, ART will use the targetPackage specified in the instrumentation APK's AndroidManifest to determine the application to be instrumented. We can perform this check in Bazel at execution time, before the apps are loaded onto the device.
See android_instrumentation_test_integration_test.sh for the e2e example.
GITHUB: https://github.com/bazelbuild/bazel/issues/903
RELNOTES: None.
PiperOrigin-RevId: 179564246
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179557378
|
|
|
|
|
|
|
|
|
|
| |
Instead of every package using the root repository's prelude, it is resolved in each repository for the packages in that repository.
There weren't any tests using the prelude at all, so these are better than nothing. I wrote them as bash integration tests instead of Java tests because I couldn't get the prelude to work at all with `BuildViewTestCase` -- I'd be happy to share the busted test I wrote if someone would like to help debug it.
Closes #3991.
PiperOrigin-RevId: 179557018
|
|
|
|
| |
PiperOrigin-RevId: 179556225
|
|
|
|
|
|
| |
This is required to migrate the c++ rules to use platform based toolchain selection.
PiperOrigin-RevId: 179552579
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #4322, #4306.
*** Reason for rollback ***
Introduces a deadlock (see https://github.com/bazelbuild/bazel/issues/4322)
*** Original change description ***
Make FileSystem operate on LocalPath instead of Path.
PiperOrigin-RevId: 179549866
|
|
|
|
|
|
| |
And fix the tests that were doing this.
PiperOrigin-RevId: 179548691
|
|
|
|
|
|
|
|
|
|
|
|
| |
--auth_scopes can be passed a comma-separated list of authentication
scopes.
Add "https://www.googleapis.com/auth/devstorage.read_write" to the list
of defaults. This scope is used when using Google Cloud Storage (GCS) as
a remote caching backend.
Change-Id: I62e6fed28b28737823ad6c70cbc5048b3a3190b5
PiperOrigin-RevId: 179548090
|
|
|
|
|
|
|
|
|
|
|
| |
Call it what it is.
RELNOTES: --remote_rest_cache was renamed to --remote_http_cache. Both
options keep working in this release, but --remote_rest_cache will be
removed in the next release.
Change-Id: I9e0b947f2184e0d543e7e19c5c33b6aa851d47d2
PiperOrigin-RevId: 179542826
|
|
|
|
| |
PiperOrigin-RevId: 179542482
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179534164
|
|
|
|
|
|
|
|
| |
There's no point in having this option. We'll use as many TCP
connections as we'll need. Fewer options FTW.
Change-Id: I502eadd6a3a35040c7eda05ef49320b273ac26ad
PiperOrigin-RevId: 179533022
|
|
|
|
|
|
|
|
| |
Inline SourceCategory.CC action configs, as CC is the only source category that
is ever passed to this method.
RELNOTES: None.
PiperOrigin-RevId: 179522955
|
|
|
|
|
|
|
|
| |
- Mention sandboxing for remote caching/execution.
- Mention buchgr/bazel-remote-cache as a remote caching backend.
RELNOTES: None.
PiperOrigin-RevId: 179515966
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179468685
|
|
|
|
|
|
|
| |
Add a safe varargs annotation. Use more precise type signature for ObjectCodecTester#verifyDeserialized and AbstractObjectCodecTest#verifyDeserialization.
RELNOTES: None
PiperOrigin-RevId: 179460437
|
|
|
|
|
|
| |
RELNOTES[INC]: --android_sdk no longer supports filegroup targets.
PiperOrigin-RevId: 179451275
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179448100
|
|
|
|
|
|
| |
this assumption doesn't hold under JDK 9.
PiperOrigin-RevId: 179443947
|
|
|
|
|
|
|
|
| |
We need to handle neverlink libraries in java_common (see #3735). Therefore JavaInfo needs to store the neverlink information. Instead of wrapping yet
another provider (JavaNeverlinkInfoProvider) into JavaInfo, store the neverlink
value directly.
PiperOrigin-RevId: 179439005
|
|
|
|
|
|
|
| |
The action cache prefix is "ac", not "actioncache".
Change-Id: I841a026133ab3b4ec5b58a0cf29252dae49434fe
PiperOrigin-RevId: 179437730
|
|
|
|
|
|
|
|
|
| |
9bb93ee8c0edae911f9e2adeaca8aebd406788b6 ("Remove the deprecated set
constructor from Skylark") completely removed the deprecated
constructor, so it doesn't seem worth mentioning anymore.
Change-Id: Iaad8a05d099ad77fde898fd9e92addf753863211
PiperOrigin-RevId: 179434966
|
|
|
|
|
|
|
|
| |
Describe the HTTP protocol in some detail.
Also improve the wording of remote caching a bit.
RELNOTES: None.
PiperOrigin-RevId: 179433738
|
|
|
|
|
|
|
| |
Part of #4128.
Change-Id: Ic46d2db2017b6cf4c14a91653ab75b3381b80b5a
PiperOrigin-RevId: 179426362
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179425421
|
|
|
|
|
|
| |
required to migrate the c++ rules onto platform-based toolchain resolution.
PiperOrigin-RevId: 179422935
|
|
|
|
| |
PiperOrigin-RevId: 179416493
|
|
|
|
|
|
|
|
| |
This is a partial rollback of https://github.com/bazelbuild/bazel/commit/e8d32b7c922f65539b74357711d5ad6b70934115, only the CommandHelper change.
Progress on #2475.
PiperOrigin-RevId: 179413908
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for Google Cloud Storage (GCS) as a HTTP caching backend.
This commit mainly adds the infrastructure necessary to authenticate
to GCS.
Using GCS as a caching backend works as follows:
1) Create a new GCS bucket.
2) Create a service account that can read and write to the GCS bucket
and generate a JSON credentials file for it.
3) Invoke Bazel as follows:
bazel build
--remote_rest_cache=https://storage.googleapis.com/<bucket>
--auth_enabled
--auth_scope=https://www.googleapis.com/auth/devstorage.read_write
--auth_credentials=</path/to/creds.json>
I'll add simplification's and docs in a subsequent commit.
Change-Id: Ie827d7946a2193b97ea7d9aa72eb15f09de2164d
PiperOrigin-RevId: 179406380
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/d6ac11dab81ec40e9adc717575904574c6c9dc48.
RELNOTES:none
PiperOrigin-RevId: 179401717
|
|
|
|
|
|
|
| |
Note that this implies that databinding cannot be used on resources in the test apk. However, the resources in the test apk are already very weird - so I don't think this makes them much weirder.
RELNOTES: None
PiperOrigin-RevId: 179243983
|
|
|
|
|
|
| |
If we are running with a single source root and not going to set up the execroot (since we know how to resolve all packages), we can avoid tracking loaded packages, since they're only used to set up the execroot.
PiperOrigin-RevId: 179234932
|
|
|
|
|
|
|
| |
Fixes #4176 (https://github.com/bazelbuild/bazel/issues/4176).
Closes #4236.
PiperOrigin-RevId: 179218605
|
|
|
|
|
|
| |
Make sure all sentences are capitalised and end with a point
PiperOrigin-RevId: 179214070
|
|
|
|
| |
PiperOrigin-RevId: 179213789
|
|
|
|
|
|
|
|
|
|
|
| |
The only use case was for Objective-C rules so that different set of sources specified in the same rule could be compiled with either ARC or no ARC. To replace source specific build variables, we call into CcLibraryHelper twice for each set of sources.
This has led to separating the building of compilation providers and outputs from those related to linking. In the case of Objective-C, the compilation outputs are merged and then passed to a single invocation of linking in CcLibraryHelper.
In a later CL, the distinction between compilation and linking will be refined by separating them in different classes.
RELNOTES:none
PiperOrigin-RevId: 179167102
|
|
|
|
| |
PiperOrigin-RevId: 179082062
|
|
|
|
|
|
|
|
|
| |
New name clears the namespace a 2nd flag that will wipe the build graph after the build. The old name would be confusing as it could easily apply to that, and so needs to be more specifically just about tracking state in the first place. The new flag can be clearly separate and about keeping state after the build.
Partial roll forward of https://github.com/bazelbuild/bazel/commit/9321316b34767b06c3071b2cf2a4de189874fcce, with fixes to documentation that are still relevant.
RELNOTES: Rename --keep_incrementality_data to --track_incremental_state
PiperOrigin-RevId: 179078292
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/c6b6dbadd0a93936c51154b25abc5fbba8f2d1af)
We accepted these by environment variable largely because setting it via invocation policy would require changing invocation policy for each command, which had caused the Bazel server to restart, loosing incremental state. This is fixed: changing invocation policy no longer causes Bazel to restart its servers, so accept these as normal options.
We will soon no longer accept these flags by environment variable, but will accept both for a transition period, so that nobody relying on these values is broken by a single release. To inform users of this environment variable, anyone setting the environment variable without the flag will receive a warning but the value will be kept. The following release will no longer accept an environment variable.
Note on format: invocation_id we accept only clean UUIDs, but for build_request_id, to help differentiate otherwise undifferentiable id types, we accept arbitrary prefixes before the UUID. The user is responsible for picking prefixes that are sane.
RELNOTES: None.
PiperOrigin-RevId: 179063120
|
|
|
|
|
|
|
|
| |
system.
This is the only place that should actually need it.
PiperOrigin-RevId: 179054861
|
|
|
|
| |
PiperOrigin-RevId: 179053724
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before:
____Waiting for build event protocol upload: 0s
____Waiting for Build Event Protocol upload to finish.
____Build Event Protocol upload finished successfully.
After:
____Waiting for Build Event Protocol upload: 0s
____Waiting for Build Event Protocol upload to finish.
____Build Event Protocol upload finished successfully.
RELNOTES: None.
PiperOrigin-RevId: 179049827
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 179046403
|
|
|
|
| |
PiperOrigin-RevId: 179042182
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Argument mixes string and array. Use * or separate argument.
- Quote the grep pattern so the shell won't interpret it.
- Use "${var:?}" to ensure this never expands to /* .
- > is for string comparisons. Use -gt instead.
- Quote the parameter to -name so the shell won't interpret it.
Closes #4163.
PiperOrigin-RevId: 179042046
|