| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
With the prereq work behind this, this is surprisingly straightforward. The main change
is to eliminate BuildConfiguration.SplittableTransitionApplier, make both DynamicTransitionApplier and StaticTransitionApplier split-aware, and add awareness of this to ConfiguredTargetFunction.trimConfigurations.
Latebound splits will follow next.
--
MOS_MIGRATED_REVID=129480309
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129473820
|
|
|
|
|
|
|
| |
--
Change-Id: Id626d41b0af9861a0e79022dcb48cffaa8c12e3a
Reviewed-on: https://bazel-review.googlesource.com/#/c/4260/4
MOS_MIGRATED_REVID=129458423
|
|
|
|
|
|
|
|
|
|
|
| |
a property without installing a different security manager.
This is required to run JUnit's tests in Blaze.
RELNOTES: Test targets can disable the JUnit4 test security manager via a property.
--
MOS_MIGRATED_REVID=129453237
|
|
|
|
|
|
|
| |
--
Change-Id: I1a904d19e1a63eff8c245bac3c18eb4ce9838912
Reviewed-on: https://bazel-review.googlesource.com/#/c/4271/
MOS_MIGRATED_REVID=129451413
|
|
|
|
|
|
|
| |
--
Change-Id: Id1f37cfe4dcb77a4af0465028f6b17e574b85954
Reviewed-on: https://bazel-review.googlesource.com/#/c/4191/
MOS_MIGRATED_REVID=129442887
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129438985
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129436348
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The underlying issue (wrong operator '==' instead of '=' for test (a.k.a '[')) was fixed by commit 31b059fc07831f86be951609128b7cd51613df98 which removed the offending code completely.
*** Original change description ***
Revert build-runfiles to use /bin/bash
If /bin/sh is dash (default on Ubuntu), this output a lot of garbage error, which make thing that the dummy build-runfiles is incorrect.
See http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=ubuntu_15.10-x86_64/731/console
--
MOS_MIGRATED_REVID=129432905
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129432777
|
|
|
|
|
|
| |
--
Reviewed-on: https://bazel-review.googlesource.com/#/c/4250/5
MOS_MIGRATED_REVID=129431153
|
|
|
|
|
|
|
|
|
| |
If /bin/sh is dash (default on Ubuntu), this output a lot of garbage error, which make thing that the dummy build-runfiles is incorrect.
See http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=ubuntu_15.10-x86_64/731/console
--
MOS_MIGRATED_REVID=129430198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129429378
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129426286
|
|
|
|
|
|
|
|
|
| |
It has been superseded by gRPC.
RELNOTES[INC]: Blaze doesn't support Unix domain sockets for communication between its client and server anymore. Therefore, the --command_port command line argument doesn't accept -1 as a valid value anymore.
--
MOS_MIGRATED_REVID=129424092
|
|
|
|
|
|
|
| |
So it stop suggesting that it is hard to write rules, though it is not easy to write good rules :)
--
MOS_MIGRATED_REVID=129423968
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129423168
|
|
|
|
|
|
|
|
|
| |
The multi-layered transformation (base -> base.pic -> base.pic.pcm -> base.pic.pcm.d) is kinda ugly, but is preferable to having 22 separate, mostly orthogonal artifact categories.
It's actually untested what happens if we put these new name patterns into the CROSSTOOL file.
--
MOS_MIGRATED_REVID=129423055
|
|
|
|
|
|
|
| |
This in preparation to DeclaredProviders implementation.
--
MOS_MIGRATED_REVID=129420617
|
|
|
|
|
|
|
| |
time without prior notice.
--
MOS_MIGRATED_REVID=129409727
|
|
|
|
|
|
|
| |
RELNOTES[INC]: Skylark: It is an error to shadow a global variable with a local variable after the global has already been accessed in the function.
--
MOS_MIGRATED_REVID=129365195
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129360870
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The Play Store serving team doesn't want to add support for any new density buckets, so I'm going to roll this back for now (this CL allows us to build an APK declaring 340, but the APK can't be pushed to the Play Store, so not very useful). I can roll forward again in the unlikely event that the Play Store folks change their mind.
I will investigate some other build solution for getting an APK into the play store that can be offered to devices declaring 340 dpi.
*** Original change description ***
Adds support for round and 340dpi to resource qualifiers, and allows stamping 340dpi into the density filtered manifest.
Also adds 340dpi to the list of supported Android Wear densities.
340dpi is the density declared by Nemo and Swordfish, and the Play Store will not offer APKs to those devices unless they include <compatible-screens> entries with this density.
--
MOS_MIGRATED_REVID=129354693
|
|
|
|
|
|
|
| |
#1603
--
MOS_MIGRATED_REVID=129331613
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129331086
|
|
|
|
|
|
|
| |
Move not performance-critical code to the input_jar.cc.
--
MOS_MIGRATED_REVID=129329869
|
|
|
|
|
|
|
|
|
|
| |
This just add the support on the Skylark side, the documentation generator
still needs to be updated.
--
Change-Id: Ic26547cdb8d2c5c01839a4014c10f1b9b209b92b
Reviewed-on: https://bazel-review.googlesource.com/#/c/4247/
MOS_MIGRATED_REVID=129328278
|
|
|
|
|
|
|
|
|
|
| |
using --build_python_zip to specify it, by default it's enabled on
Windows and disabled on other platforms.
--
Change-Id: Ib992edaf70c08568816b973159a429ff7165eed8
Reviewed-on: https://bazel-review.googlesource.com/#/c/4244
MOS_MIGRATED_REVID=129326115
|
|
|
|
|
|
|
|
|
|
|
| |
Examples for how to use <zip_path>=<file> syntax:
zipper c x.zip a/b/__init__.py= # Add an empty file at a/b/__init__.py
zipper c x.zip a/b/main.py=foo/bar/bin.py # Add file foo/bar/bin.py at a/b/main.py
--
Change-Id: I3c09dfb31d082f3ca8036e87affc8d99f7e75fe0
Reviewed-on: https://bazel-review.googlesource.com/#/c/4243
MOS_MIGRATED_REVID=129325719
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129320850
|
|
|
|
|
|
|
|
|
| |
bootstrap.
Previously, we deleted the temp dir and after that, we tried to print errfile in it, and were surprised that it didn't exist.
--
MOS_MIGRATED_REVID=129320375
|
|
|
|
|
|
|
| |
on Windows by default)
--
MOS_MIGRATED_REVID=129319018
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129316675
|
|
|
|
|
|
|
|
|
| |
bootstrapping.
It apparently happened not to make a difference, but still.
--
MOS_MIGRATED_REVID=129314926
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129313959
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129305218
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with
dynamic configs.
The old code incorrectly applied a no-op instead of hard-setting a specific config.
Testing: This is a prereq piece for the main change adding dynamic split transitions. Once
we have that change, standard Bazel tests over implemented late-bound split attributes
(e.g. AppleBinaryRule: ":cc_toolchain") will provide proper coverage. There's no easy way
to test this directly since the affected code won't really work until the dynamic split change is in.
--
MOS_MIGRATED_REVID=129278253
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129228122
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129226221
|
|
|
|
|
|
|
| |
instead of a hardcoded switch. Add action configs to CppConfiguration for each link type.
--
MOS_MIGRATED_REVID=129221108
|
|
|
|
|
|
|
| |
--
Change-Id: I3ed7407826b433df6118310872634ad4706939d0
Reviewed-on: https://bazel-review.googlesource.com/#/c/4246/
MOS_MIGRATED_REVID=129217952
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129217657
|
|
|
|
|
|
|
| |
It's still used in one place and should be removed completely in October.
--
MOS_MIGRATED_REVID=129207133
|
|
|
|
|
|
|
| |
sandbox will not allow us to bind to the IPv4 one. Automatically falls back to IPv4 if binding to [::1] fails.
--
MOS_MIGRATED_REVID=129206917
|
|
|
|
|
|
|
| |
the PackageLookupValue to reduce the number of references to the filename "BUILD".
--
MOS_MIGRATED_REVID=129203257
|
|
|
|
|
|
|
|
| |
The goal is to remove parse and eval functions from Environment, as well as
isSkylark boolean.
--
MOS_MIGRATED_REVID=129202204
|
|
|
|
|
|
|
| |
We actually don't need it.
--
MOS_MIGRATED_REVID=129149261
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
config is missing required fragments.
Before this change, Bazel crashes with the mysterious error: "Fragment
foo can't load missing options BarOptions" with no details on which target or dep
needed Foo. So figuring out the source of the error is painful.
With this change, we instead get:
//foo:foo: dependency //bar:bar from attribute "deps" is missing required config fragments: JavaConfiguration
--
MOS_MIGRATED_REVID=129143764
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129141770
|
|
|
|
|
|
|
|
|
|
|
| |
This can be used in conjunction with apple_binary to add watchOS2 extensions to an ios application bundle.
This is the majority of the native work for this bundling logic. Before announcing general availability of this feature, we will want to:
1. Iterate with teams who have existing watchOS2 apps to catch any corner-case bugs
2. Introduce a skylark macro to wrap apple_watch2_extension and apple_binary into a single rule; this will both serve as a convenience and ensure users set the appropriate linkopts and platformtype on their apple_binary target.
--
MOS_MIGRATED_REVID=129122855
|