| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/4439.
Empty assets are handled by writing out an empty file named "assets/empty_asset_generated_by_bazel~", which will silently be ignored by AAPT.
RELNOTES: aar_import now supports assets.
PiperOrigin-RevId: 182110400
|
|
|
|
|
|
| |
We stopped treating empty files specially in the execution phase after unknown commit. So this code is mostly if not entirely orphaned. The only scenario in which this would lead to a semantic difference that I can think of is if the user is running with --nouse_action_cache and a running Bazel server, and they have an action they want to re-run when an empty input file changes, which isn't something we need to be concerned about.
PiperOrigin-RevId: 182109952
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 182100169
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 182099868
|
|
|
|
| |
PiperOrigin-RevId: 182099803
|
|
|
|
|
|
| |
Post to the Skyframe Environment instead.
PiperOrigin-RevId: 182096559
|
|
|
|
|
|
|
|
|
| |
dexbuilder action by default).
Binaries can opt in by adding "incremental_dexing = 1" attribute.
RELNOTES: Proguarded Android binaries can be built with incremental dexing.
PiperOrigin-RevId: 182092699
|
|
|
|
| |
PiperOrigin-RevId: 182087153
|
|
|
|
|
|
|
|
|
|
|
|
| |
test_android_ndk_repository_wrong_path presumes the wrong ndk path
'some_dir' to not exist. This test will work initially, but break if run
incrementally, because of the some_dir remaining in the TEST_SRCDIR (the
runfiles root for this test). Switching this over to use the ephemeral
TEST_TMPDIR instead.
Closes #4465.
PiperOrigin-RevId: 182083666
|
|
|
|
|
|
|
| |
required for all attributes marked executable.
RELNOTES: None
PiperOrigin-RevId: 182082917
|
|
|
|
|
|
| |
This is slightly more descriptive, and we will potentially want to use the name Root for a broader concept shared between ArtifactRoot and RootedPath.
PiperOrigin-RevId: 182082367
|
|
|
|
|
|
|
|
| |
Issue #4401
Closes #4437.
PiperOrigin-RevId: 182067976
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel-toolchains/releases/tag/f3b0970
PiperOrigin-RevId: 182058527
|
|
|
|
|
|
|
| |
If two values compared equal (e.g., MethodLibrary#bool and SkylarkAttr#bool), we were dropping one of them in favor of the other.
RELNOTES: None
PiperOrigin-RevId: 182057611
|
|
|
|
|
|
|
| |
SerializationCodeGenerator, which is a generalization of Marshaller that
supports primitive and array values.
PiperOrigin-RevId: 182053617
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 182051418
|
|
|
|
|
| |
Change-Id: I5fa8412fe0673b71a6e17adb39be0a208ee54f63
PiperOrigin-RevId: 182048035
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 182044727
|
|
|
|
|
|
|
| |
can be attached to C++ compile actions without tickling the bug that makes Blaze crash when extra actions are attached to shared actions that do input discovery.
RELNOTES: None.
PiperOrigin-RevId: 182044169
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel CI (https://ci.bazel.build/job/bazel-tests/1722/)
*** Original change description ***
Report unsuccessful error code if bazel fetch fails in "keep going" mode.
Fixes #3234.
PiperOrigin-RevId: 182042503
|
|
|
|
|
|
|
|
|
|
|
| |
Support applying a sequence of commands to an http_archive,
after the patch files are applied. In this way, tasks like
shebang-fixes can easily be added.
Fixes #3395.
Change-Id: Ifdad584a852efd425c436d57ef71a0d681488629
PiperOrigin-RevId: 182037265
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 182033773
|
|
|
|
|
|
|
| |
Fixes #3234.
Change-Id: I1bfbe856d35b98995f5a0684fe47c7566b8dd093
PiperOrigin-RevId: 182029085
|
|
|
|
|
|
|
|
|
|
| |
Added tests for checking JavaSourceJarsProvider state.
All other providers will be implemented in next CLs.
previous CL with JavaCompilationArgsProvider implementation is https://github.com/bazelbuild/bazel/commit/32dff21d00ad7d1bdf50e8761d675a6e7e002de9
RELNOTES:none
PiperOrigin-RevId: 182028182
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also make most targets in `//src/tools/runfiles`
private. The user should depend on
`@bazel_tools//tools/runfiles:$LANG-runfiles`
instead.
See https://github.com/bazelbuild/bazel/issues/4460
RELNOTES[NEW]: java,runfiles: You can now depend on `@bazel_tools//tools/runfiles:java-runfiles` to get a platform-independent runfiles library for Java. See JavaDoc of https://github.com/bazelbuild/bazel/blob/master/src/tools/runfiles/java/com/google/devtools/build/runfiles/Runfiles.java for usage information.
Change-Id: Iba9113453222ae74ce42a324272711f613104891
PiperOrigin-RevId: 182022851
|
|
|
|
|
|
|
|
| |
This method violates the invariant that derived roots are never equal to the exec root. Only source roots can be equal to the exec root.
Note that this method was only used in tests, so this CL should be completely safe as long as its tests pass.
PiperOrigin-RevId: 181998483
|
|
|
|
|
|
| |
In this case, the invariant violated is creating derived roots at the exec root.
PiperOrigin-RevId: 181994080
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181990193
|
|
|
|
| |
PiperOrigin-RevId: 181975994
|
|
|
|
|
|
|
|
|
|
|
| |
Support applying a sequence of patches for external repositories
imported via http_archive. (Note that we only support the version
from @bazel_tools, not the deprecated native rules.)
Works towards #3395.
Change-Id: I96c746acc04790b051eb686856c04a3ff3c90059
PiperOrigin-RevId: 181975322
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181973847
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 181971087
|
|
|
|
|
| |
Change-Id: Id3d6e6da60aca3c02c7cf3e9e727ecbf177dde66
PiperOrigin-RevId: 181971084
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cut all dependencies of the Java runfiles library,
so we can include its sources in @bazel_tools, and
any Java project can safely depend on it without
worrying about pulling in an incompatible version
of Guava for example.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I4a9314c56a2c9dc3afdf53669429750d8fb81e3b
PiperOrigin-RevId: 181968558
|
|
|
|
|
|
|
| |
The default is SMALL, and for better or worse, we mark BuildViewTestCase tests
as small, and BuildIntegrationTestCase tests as medium.
PiperOrigin-RevId: 181966013
|
|
|
|
|
|
|
| |
Fixes #3699.
Change-Id: I44028476be96037334a1ae48de450d625925676f
PiperOrigin-RevId: 181962926
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/4376
Change-Id: Id78bb0930044626304e54f07735db4d4b2c84720
PiperOrigin-RevId: 181959528
|
|
|
|
|
|
|
|
|
|
| |
Work towards #3676.
The behavior is still incorrect (we should in fact disallow this), but
at least there is no hard crash.
Change-Id: I5181dba73ad725d20b2ea82b2f19e86664b9dbff
PiperOrigin-RevId: 181954820
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add ":windows_tests" and ":all_windows_tests"
rules to these packages, and include them in the
parent packages.
Fixes https://github.com/bazelbuild/bazel/issues/4127
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I9c454ed21f47feb8e88e1c25b1e4fa216baa38f6
PiperOrigin-RevId: 181951525
|
|
|
|
|
|
|
| |
Fixes #3836.
Change-Id: Icc9e8e08c4336fc20f46b6b878986b991d62ab18
PiperOrigin-RevId: 181949937
|
|
|
|
|
|
|
|
|
| |
Change-Id: Ib8dd9265b18fa0915f52427567845105fcdfa295
Closes #4447.
Change-Id: Ib8dd9265b18fa0915f52427567845105fcdfa295
PiperOrigin-RevId: 181943004
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/3864a45afa368473a4a6a90d69edb48cb67d367a
PiperOrigin-RevId: 181940016
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Split //src/test/j/c/g/d/b/lib:foundations_test
into smaller tests, and enable many of them on
Windows.
Some tests are still tagged as "no_windows",
either because they depend on ":unix", or because
we need to fix them to pass on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: Ibfab568a9e7b939c40f1301c9cfe06e60302755c
PiperOrigin-RevId: 181936880
|
|
|
|
| |
PiperOrigin-RevId: 181908311
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
before: blaze build --nobuild //foo --experimental_post_build_query="deps(//foo)"
after: blaze cquery "deps(//foo)"
pros of ui change:
- more concise
- assumes query expression targets == targets to be built (but allows for flexibility through --top_level_targets flag)
- separate from build command
- cquery command recognizes query options, build options, and its own unique set of options
cons of ui change:
- adds another command to blaze
- recognizes options that don't actually work yet -> requires more option validation
RELNOTES: None
PiperOrigin-RevId: 181816980
|
|
|
|
|
|
|
|
|
| |
This avoids invalid layouts (non-sequential map values), and provides better separation between a layout's representation as a map and its view as a list.
Also removed a factory method that's unnecessary, now that the plan is not to closely tie SkylarkInfo to SkylarkProvider.
RELNOTES: None
PiperOrigin-RevId: 181807071
|
| |
|
|
|
|
| |
PiperOrigin-RevId: 181797078
|
|
|
|
|
|
|
|
| |
javac doesn't allow both to be set, so when defaulting to target
Java 8 use --release if the javacopts already include a
--release flag.
PiperOrigin-RevId: 181777670
|
|
|
|
|
|
|
|
|
|
| |
When checking for conflicts between an input and an output file
of a rule, honor the repository the label belongs to. It is a
perfectly valid use case to create one file from an equally named
(including path) in a different repository.
Change-Id: I3aaa99eaa0c473ec31c5cc77beacf657c41ef56d
PiperOrigin-RevId: 181761940
|