| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In many cases, users do:
d = depset()
d += ...
To catch this issue, we use a heuristic to find which variable is a depset
(in theory, it could be reassigned - but it's unlikely and that would be
error-prone anyway)
RELNOTES: None.
PiperOrigin-RevId: 179536463
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: ddd5ac16aeffa6c4693c348f73e7365240b1abc5
Cherry picks:
+ 2cf560f83922e6df9626ba3ee063c1caf6797548:
Update version of re2
+ a2d2615362c65be98629b39ce39754a325ed1c42:
Check for null build file returned from getBuildFileForPackage.
+ 68c577afc2fb33b5e66b820bcc9043fed1071456:
Fix some broken targets and failing tests.
+ 766ba8adc4487f17ebfc081aeba6f34b18b53d6c:
Automated rollback of commit
337f19cc54e77c45daa1d5f61bf0a8d3daf8268f.
+ a22d0e9c14e58b29d81f5a83bdcc6e5fce52eafe:
Fix: uploading artifacts of failed actions to remote cache
stopped working.
+ 03964c8ccb20d673add76c7f37245e837c3899b6:
[java_common.compile] Name output source jar relative to the
output jar name
Incompatible changes:
- The deprecated `set` constructor is removed, along with the
migration flag --incompatible_disallow_set_constructor. It is
still temporarily
allowed to refer to `set` from within unexecuted code.
- The flag --incompatible_disallow_set_constructor is no longer
available, the deprecated `set` constructor is not available
anymore.
- The path to the JVM executable is not accessible anymore as
ctx.{fragments,host_fragments}.jvm.java_executable. Use
JavaRuntimeInfo.java_executable_exec_path instead.
- --clean_style is no longer an option.
New features:
- Users can use win_def_file attribute to specify a DEF file for
exporting symbols when build a shared library on Windows.
- Add --experimental_android_resource_cycle_shrinking option to
allow for more aggressive code and resource shrinking.
Important changes:
- Late-bound attributes are exposed to skylark. This is a new API
(`configuration_field()`) to depend on certain
configuration-defined targets from skylark rules.
- Document interaction between test_suite and target exclusions
- AAR manifest files will come from the processed resource APK if it
exists.
RELNOTES: None for Blaze users.
- Document interaction between test_suite and target exclusions
- --keep_incrementality_data flag allows Bazel servers to be run in
memory-saving non-incremental mode independent of --batch and
--discard_analysis_cache.
- Add deps attribute to Skylark maven_aar and maven_jar workspace
rules.
- Use --expand_configs_in_place as a startup argument to change the
order in which --config expansions are interpreted.
- SOURCE_DATE_EPOCH
(https://reproducible-builds.org/specs/source-date-epoch/) can
be used to override the timestamp used for stamped target (when
using --stamp).
- Package specifications can now be prefixed with `-` to indicate
negation
- transitive_source_jars is now exposed on JavaInfo.
- Add six to deps of has_services=1 py_proto_librarys.
- java_tests no complain when use_testrunner is explicitly set to 1
and main_class is set.
- transitive_source_jars is now exposed on JavaInfo.
- Debug messages generated by `print()` are not being filtered out
by --output_filter anymore, it's recommended not to use them in
production code.
- in the Label() function, relative_to_caller_repository is now
deprecated.
- java_tests no complain when use_testrunner is explicitly set to 1
and main_class is set.
- Bazel's default hash function was changed from MD5 to SHA256.
In particular, this affects users of remote caching and
execution, as
all hashes will be SHA256 by default.
- Remove redirects for domains be.bazel.build and cr.bazel.build
from the source for docs.bazel.build (because those subdomains
don't resolve here; they resolve to bazel.build, which has the
redirects for them)
- First argument of 'load' must be a label. Path syntax is removed.
(label should start with '//' or ':').
- Document startup option --host_javabase
- The --host_platform and --platform flags are no longer
experimental.
|
|
|
|
|
|
|
|
| |
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: 179487151
|
|
|
|
|
|
|
| |
These two action types, 'linkstamp-compile' and 'c++-link-interface-dynamic-library', require use of the wrapped_clang tool, which requires apple_env to be set.
RELNOTES: None.
PiperOrigin-RevId: 179475470
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
implementations don't store rdeps for done nodes.
RELNOTES: None
PiperOrigin-RevId: 179455698
|
|
|
|
|
|
| |
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
|
|
|
|
| |
PiperOrigin-RevId: 179438278
|
|
|
|
|
|
|
| |
The action cache prefix is "ac", not "actioncache".
Change-Id: I841a026133ab3b4ec5b58a0cf29252dae49434fe
PiperOrigin-RevId: 179437730
|
|
|
|
|
|
|
|
|
| |
Fixes #4097.
Fixes part of #4310.
Closes #4265.
PiperOrigin-RevId: 179437184
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: Ib470babdfe0d9aac328ead7f378fe281532d3b7e
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: Ifc4a00d5bfef974f82c06eebc9553edad7b8145e
|
|
|
|
|
|
|
|
| |
- BAZEL is written with a single Z
- add missing equals symbol in the first argument to env
Change-Id: Ib18a2cca306d9a0eee38416ce38565b530d8e5c6
PiperOrigin-RevId: 179341099
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke some cakemix tap projects
*** Original change description ***
Use assets from the APK for resource shrinking rather than from the merge actions.
RELNOTES: none
PiperOrigin-RevId: 179252805
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179245378
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
bound (because of interference).
RELNOTES: None.
PiperOrigin-RevId: 179229423
|
|
|
|
|
|
|
| |
actions.
RELNOTES: none
PiperOrigin-RevId: 179227857
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179200616
|
|
|
|
| |
PiperOrigin-RevId: 179190405
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the google http client to a custom built binary. It's the sources
from version 1.22.0 with one cherry-pick [1]. The cherry-pick makes
google http client compatible with the apache http client version we are
using.
The next release of google http client will contain this commit and from
there on we can just stick to their release version again.
[1]
https://github.com/google/google-http-java-client/commit/4b5f59ed042d3b55b3148a1b01f1d5ee0ad7460c
Change-Id: If6273be78b716dd417a60096599c036cc8101efb
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bootstrap-distfile test aims at verifying the completeness of
the distribution archive. The functionality of workers is a different
issue, so separate those concerns and do the test bootstrap in a
simple setup, calling javac standalone (see #1250). Also, reduce
the output to make the test log more readable.
Improves on #4306.
Change-Id: I839523628cd35f2deefc1a4dfdf0cf58a4d1f51a
PiperOrigin-RevId: 179186615
|
|
|
|
|
|
|
| |
Also remove references to old-style depset.
RELNOTES: None.
PiperOrigin-RevId: 179184967
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 179174976
|
|
|
|
|
|
|
|
|
|
|
| |
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
|