aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Adds external J2ObjC BUILD files to Bazel's generated embedded_tools directory,Gravatar Googler2017-05-31
| | | | | | | and fixes some of J2ObjC's implicit deps to correctly reference the embedded tools. RELNOTES: Partially fixes external J2ObjC support. PiperOrigin-RevId: 157503022
* When filtering resources in analysis, also filter resource rootsGravatar Googler2017-05-31
| | | | | | | | | | | | | | | | | If all resources from a directory are filtered out, the resource processing action should not receive a reference to that directory. Filtering the entire contents of a directory is uncommon but not impossible. It may be indicative of an error (if the user filters on a language, but only provided resources in other languages - in this case, the build should and will fail during Java compilation when the requested resource does not exist) or of weird but acceptable behavior (placing resources for some default language in one resource directory and resources for all other languages in some other directory, then inheriting both directories and filtering on language) that should be correctly handled. RELNOTES: none PiperOrigin-RevId: 157499745
* Optionally skip fallback to javac-turbineGravatar cushon2017-05-31
| | | | PiperOrigin-RevId: 157494773
* Enable desugaring try-with-resources by default.Gravatar cnsun2017-05-31
| | | | | RELNOTES: none PiperOrigin-RevId: 157490771
* Small optimization to avoid allocating strings in the bind mount loop.Gravatar Googler2017-05-31
| | | | PiperOrigin-RevId: 157479936
* Use cc implementation of singlejar except on Windows.Gravatar Xin Gao2017-05-31
| | | | | Change-Id: Ie4a2db2a6fa1ea86f4bdd42cd806f6804a0c56d4 PiperOrigin-RevId: 157473007
* Remote tests should not depend on lib:runtimeGravatar buchgr2017-05-31
| | | | | | | | Move AuthAndTLSOptions to its own package, so that tests/remote no longer depends on lib:runtime. RELNOTES: None. PiperOrigin-RevId: 157469629
* Add host platform definition that internal code can depend on.Gravatar jcater2017-05-31
| | | | | | Part of #2219. PiperOrigin-RevId: 157469326
* Small updates to external dependencies topic for readability.Gravatar Googler2017-05-31
| | | | PiperOrigin-RevId: 157468728
* Fix clean command to not use boolean optionsGravatar Googler2017-05-31
| | | | | | | Using boolean options with expansions on them meant they were still used if in the --no(flag) case. RELNOTES: Clean command no longer uses boolean values for --async, --expunge, and --expunge_async options. PiperOrigin-RevId: 157465859
* Migrate most of the assertions to Truth that the auto-migration tool did not ↵Gravatar lberki2017-05-31
| | | | | | | | | catch. IntelliJ's "replace structurally" command was surprisingly useful. RELNOTES: None. PiperOrigin-RevId: 157463734
* Fix scripts/serve-docs.shGravatar hlopko2017-05-31
| | | | | RELNOTES: None. PiperOrigin-RevId: 157463020
* Add @googleapis repository to WORKSPACEGravatar Jakob Buchgraber2017-05-31
| | | | | Change-Id: I2c588a4e965f4f0f15db8d447c63307b1baf1cd0 PiperOrigin-RevId: 157462273
* Fixes J2ObjC support. Adds a BUILD.tools and updates BUILD.remote withGravatar Keith Stanger2017-05-30
| | | | | | the necessary targets depended upon by J2ObjCAspect.java. Change-Id: I0a93378029707f0ebbda3a30b947519a385243f1
* Add FeatureSpecification.Gravatar hlopko2017-05-30
| | | | | RELNOTES: None. PiperOrigin-RevId: 157450873
* Introduce third_party/googleapisGravatar Jakob Buchgraber2017-05-30
| | | | | | | | | | | | | Add `https://github.com/googleapis/googleapis` as a third_party dependency at commit `001f6702ac4cd72194a5120ff978fcfa740783d6`. These protos are required for the upcoming open sourcing of the BES protocol code. Additionally, add (java_)proto_library() rules for the protobufs required by the BES protocol. Change-Id: Ie78a9941a62f2085a58ad859c91161885e6f390d
* Make Bazel build without --cpu=x64_windows_msvcGravatar Yun Peng2017-05-30
| | | | | | | | | | | | | | | | After this change, with a Bazel having MSVC as default toolchain, the command to build a MSVC Bazel on Windows is simply: bazel build //src:bazel although bazel build --cpu=x64_windows_msvc //src:bazel is still supported. And the command to build a MSYS Bazel on Windows is: bazel build --cpu=x64_windows_msys //src:bazel Also made //src/test/cpp:blaze_util_test pass without --cpu=x64_windows_msvc Change-Id: Iaf37513c778768d06fb5700442d5229a5f348964 PiperOrigin-RevId: 157446905
* Migrate Java tests to Truth.Gravatar lberki2017-05-30
| | | | | | RELNOTES: None. PiperOrigin-RevId: 157446717
* BEP: Correctly report test exit code.Gravatar buchgr2017-05-30
| | | | | | | | | | | | | When a test failure occurred the BEP would still report a build_finished event with exit code SUCCESS, even though bazel's exit code was TESTS_FAILED. This is because we would rely on the exit code reported by the BuildCompleteEvent. However, this exit code contains only the build status without taking into account the test status. In this change we introduce the TestingCompleteEvent that reports bazel's final exit code in case of "bazel test". RELNOTES: None. PiperOrigin-RevId: 157445808
* BES: Capture stdout/stderr.Gravatar buchgr2017-05-30
| | | | | | | | The BEP protocol currently does not include stdout/stderr when sent over BES. This change makes the BuildEventStreamer created by the BuildEventServiceModule listen in on stdout/stderr. RELNOTES: None. PiperOrigin-RevId: 157439952
* third_party/protobuf: Add proto_library for well known types.Gravatar Jakob Buchgraber2017-05-30
| | | | | | | | | | | | | | | | In order to use the build event service protobufs we need to support protobufs well known types inside bazel. Unfortunately, due to a bug in bazel's proto_library [1], protobuf can't provide such a proto_library yet [2]. We expect this patch to be committed to protobuf upstream once [1] is resolved. Bazel's proto_library bug [1] is also the reason why this change has to duplicate the well known protos under google/protobuf. [1] https://github.com/bazelbuild/bazel/issues/2265 [2] https://github.com/google/protobuf/issues/2763 Change-Id: I5e16d437f2f581f11553049be0b4bcc564f4ad96
* RemoteSpawnStrategy: don't round-trip through StringGravatar ulfjack2017-05-30
| | | | | | Instead, print the downloaded bytes directly to stdout / stderr. PiperOrigin-RevId: 157435933
* Change ProtobufSupport to use CrosstoolCompilationSupport if ↵Gravatar Googler2017-05-30
| | | | | | experimental_objc_crosstool=all PiperOrigin-RevId: 157421008
* java_stub_template: create classpath jar if neededGravatar László Csomor2017-05-30
| | | | | | | | | | | | | | Create a jar with a classpath in it if the classpath is too long. We have already been using this trick on Windows but need it on Linux/Darwin too, because OpenJDK and ZuluJDK don't support parameter file syntax. Fixes https://github.com/bazelbuild/bazel/issues/3069 Change-Id: I57c981ba798dd687118feb98ccf7f61b38b03ff4 PiperOrigin-RevId: 157403379
* Fix some typoGravatar pcloudy2017-05-30
| | | | | RELNOTES: None PiperOrigin-RevId: 157403137
* Polish the documentation addressing #3063Gravatar hlopko2017-05-30
| | | | | RELNOTES: None. PiperOrigin-RevId: 157401168
* Remote worker: skip non-existent files after action executionGravatar ulfjack2017-05-30
| | | | | | | | | | | | | | | | | Tests basically always finish with non-existent files, and this is not an error on the server side. Instead, the client (Bazel) checks whether all the files it expects are present. The test didn't catch this because it was silently falling back to local execution. Non-existent files were leading to an IOException, which caused the remote worker to log nothing, and silently return an error with no output. Log errors in the remote worker to make future debugging easier. Fixes #2887. PiperOrigin-RevId: 157400131
* Update Windows documentGravatar Yun Peng2017-05-30
| | | | | | | | | | 1. We are not high experimental any more 2. Point known issues to the right place 3. Make it clear that we also support python 3 4. MSVC is the default on Windows toolchain since 0.5.0 Change-Id: I804215b7b14263e43b30cdf76a9aaf0eb4598cee PiperOrigin-RevId: 157398506
* Do not use sed -E in bootstrap/compile.shGravatar hlopko2017-05-30
| | | | | | | Strangely enough, some clients have sed that doesn't support -E RELNOTES: None. PiperOrigin-RevId: 157397892
* For version 0.5.0, update installation instructions:Gravatar Googler2017-05-29
| | | | | | | | | - Bazel with JDK 7 will not be supported past 0.5.0 - a new installer is available with embedded JDK This change should only be submitted when version 0.5.0 is released. PiperOrigin-RevId: 157396320
* experimental UI: don't double track pending transportsGravatar Klaus Aehlig2017-05-29
| | | | | | | | | | As the state tracker keeps track of which transports we still have to wait for, make the event handler just ask the state tracker. In this way, we also handle gracefully if the closing of a transport is reported more than once. Change-Id: I0e1959d827268319ec00541994314c9325ef2307 PiperOrigin-RevId: 157395608
* Update documentation to address #3063Gravatar hlopko2017-05-29
| | | | | RELNOTES: None PiperOrigin-RevId: 157393208
* Make msysless flavour be the default inside chocolateyGravatar Peter Mounce2017-05-29
| | | | | | | | | | | | This attempts to fix #3006. This change will presumably have to be reversed once msysless binary name changes to become the default. It would be simpler to name the default binary for being default, to avoid special casing (see https://github.com/bazelbuild/bazel/issues/3006#issuecomment-301440068). Closes #3066. PiperOrigin-RevId: 157390473
* Refactor protobuf and grpc BUILD files for WindowsGravatar Yun Peng2017-05-29
| | | | | | | | 1. Added config_settings for Windows 2. Don't use gcc warning options in copts, this made it possible to build without python wrapper scripts. Change-Id: I37521d717b9d2d488a3bb0ec658dad40c6ddbb27
* Mark //s/t/s/integration:skylark_flag_test manualGravatar László Csomor2017-05-29
| | | | | | | | | This should fix Bazel CI / bazel-tests. See https://github.com/bazelbuild/bazel/issues/3072 Change-Id: I6fe2247d99d11e4e544c4066c132a251652bd2ce PiperOrigin-RevId: 157386938
* Experimental UI: Support multiple BuildEventTransportAnnouncedEventsGravatar buchgr2017-05-29
| | | | | | | | We initially didn't consider that multiple BuildEventStreamer instances might exist during a build. RELNOTES: None. PiperOrigin-RevId: 157385069
* BEP: also report make variablesGravatar Klaus Aehlig2017-05-29
| | | | | | | | | An important part of a configuration are the "make variables", containing values such as TARGET_CPU. Report them as part of the description of the configuration. Change-Id: Id918cc340acac87cf95cc66581345f8060cb4877 PiperOrigin-RevId: 157378950
* Replace list of changes in 0.5 announcement by a link to GitHub release page.Gravatar steren2017-05-29
| | | | | | | | In previous annoucenment, we did not copy the full list of changes in the blog post: https://bazel.build/blog/2016/11/02/0.4.0-release.html Here they were copies because they were temporary added to the blog post draft, but should have ultimately be removed. RELNOTES: None PiperOrigin-RevId: 157378942
* Migrate tests to Truth.Gravatar lberki2017-05-29
| | | | | | RELNOTES: None. PiperOrigin-RevId: 157378037
* Migrate tests to Truth.Gravatar lberki2017-05-29
| | | | | | RELNOTES: None. PiperOrigin-RevId: 157374805
* Remove unused method from build.shGravatar Damien Martin-Guillerez2017-05-29
| | | | | Change-Id: I21c738873b2bc6b4d2e8b607e0a206589d905f86 PiperOrigin-RevId: 157271290
* Changed a link so that the 'Docs' header on Bazel's site goes to the Bazel ↵Gravatar Googler2017-05-29
| | | | | | | | | overview topic rather than instructions for installing Bazel. Test: staged locally RELNOTES: None. PiperOrigin-RevId: 157263957
* Keep "srcs", "hdrs" and "textual_hdrs" separate.Gravatar Googler2017-05-29
| | | | | | | | | | Each can has slightly different semantics for the IDE, and it is better to use the information on which files belong to which group from BUILD file rather than use heuristics like file extension to determine it. The contents of "textual_hdrs" are added by the prefetcher. RELNOTES: None. PiperOrigin-RevId: 157256048
* Delete ios_framework native rule.Gravatar cparsons2017-05-29
| | | | | RELNOTES: ios_framework native rule has been removed. This rule had been essentially broken for several months now; users should be using the skylark ios framework rule. https://github.com/bazelbuild/rules_apple has details. PiperOrigin-RevId: 157246539
* Propagate objc_library SDK Frameworks through cc_library edgesGravatar cparsons2017-05-29
| | | | | RELNOTES: None. PiperOrigin-RevId: 157235505
* Make workspace cycle reporting a little more flexibleGravatar kchodorow2017-05-29
| | | | | | Fixes #2999. PiperOrigin-RevId: 157222957
* Add bazel 0.5.0 release blog postGravatar hlopko2017-05-26
| | | | | RELNOTES: None. PiperOrigin-RevId: 157219345
* For objc rules, generated headers are mandatory inputs to CppCompileAction.Gravatar cpeyser2017-05-26
| | | | PiperOrigin-RevId: 157218175
* fixed broken "compile bazel from source" in "ubuntu" pageGravatar Or Shachar2017-05-26
| | | | | | Closes #3052. PiperOrigin-RevId: 157210157
* Release 0.5.0 (2017-05-26)Gravatar Bazel Release System2017-05-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Baseline: f3ae88ee043846e7acdffd645137075a4e72c573 Cherry picks: + c58ba098526b748f9c73e6229cafd74748205aa1: Release to GCS: put the final release in its own directory + 0acead4ea3631240659836ce6ecd6d7f67fd352b: Update protobuf to latest master at a64497c and apply @laszlocsomor's latest changes from https://github.com/google/protobuf/pull/2969 on top of it. + d0242ce4a87929f2528f4602d0fb09d1ccfcea94: Make symlinks consistent + d953ca8b87a46decbce385cebb446ae0dd390881: Clean VanillaJavaBuilder output directories + 755669fb5de1f4e762f27c19776cac9f410fcb94: Pass all the environment variable to Bazel during bootstrapping + 6f041661ca159903691fcb443d86dc7b6454253d: Do not mark the JDK7 installer -without-jdk-installer + 720561113bfa702acfc2ca24ce3cc3fd7ee9c115: Fix #2958: Installer should not overwrite bazelrc + 511c35b46cead500d4e76706e0a709e50995ceba: Bootstrap: move the fail function to the top + 8470be1122825aae8ad0903dd1e1e2a90cce47d2: Clean up javac and Error Prone targets + 4a404de2c6c38735167e17ab41be45ef6fc4713a: Update javac version to 9-dev-r4023-2 + 36ce4b433e19498a78c34540d5a166d4e0006b22: Update javac version to 9-dev-r4023-2 + 38949b8526bdb3e6db22f3846aac87162c28c33f: Migrate off versioned javac and Error Prone targets + 1a57d298f8aa6ea8136d93223902104f2479cd2a: Re-enabling passing -sourcepath via javacopts. + eb565f408e03125e92d42b00756e519795be6593: Make make sure that msys build actually builds msys version + 39f328cf392056618d1a3ead4835a138b189a06d: Fix typo. Also do not override host_cpu for msvc. + 624802893f4fe72118f00a78452605d41a2e1c6f: Select correct JDK for windows_msys + c4f271d1a68366b6fa5ff38ea7d951b6a22af044: Automated g4 rollback of commit 3e5edafa2a04a71cd3596e929e83222da725f3f9. + 926180997a0f296a5a009326aead887279ce0a90: Remove process-tools.cc which I forgot to delete during the last rollback. + baca6e4cb023649920871b74810927d304729e59: Fix #2982: Bazel installer should not check for installed JDK if using a bundled JDK. + 866ecc8c3d5e0b899e3f0c9c6b2265f16daae842: Disable msys path conversion on Windows. + cc21998c299b4d1f97df37b961552ff8168da17f: Rollforward #2 of: Basic open-source crosstool to support targeting apple platform types. + 0f0ccc4fc8229c1860a9c9b58089d6cfb2ee971f: Escape % in strings that will appear in Crosstool + 3b08f774e7938928e3a240a47a0a7554cdc8d50b: Adding feature for linking C Run-Time library on Windows Incompatible changes: - Bazel's Linux sandbox no longer mounts an empty tmpfs on /tmp, instead the existing /tmp is mounted read-write. If you prefer to have a tmpfs on /tmp for sandboxed actions for increased hermeticity, please use the flag --sandbox_tmpfs_path=/tmp. - Converting artifacts to strings and printing them now return "File" instead of "Artifact" to be consistent with the type name. - The return type of depset.to_list() is now a list rather than a frozen list. (Modifying the list has no effect on the depset.) - Bazel now prints logs in single lines to java.log - --use_dash, --dash_url and --dash_secret are removed. - Remote repositories must define any remote repositories they themselves use (e.g., if @x//:foo depends on @y//:bar, @y must be defined in @x's WORKSPACE file). - Remote repositories must define any remote repositories they themselves use (e.g., if @x//:foo depends on @y//:bar, @y must be defined in @x's WORKSPACE file). - objc_xcodeproj has been removed, use tulsi.bazel.build instead. New features: - If grte_top is a label, it can now follow non-configurable redirects. - Optional coverage_files attribute to cc_toolchain - "query --output=build" now includes select()s - Raw LLVM profiles are now supported. Important changes: - Automatically generate Proguard mapping when resource shrinking and Proguard are enabled. - New rules in Bazel: proto_library, java_lite_proto_library, java_proto_library and cc_proto_library - Activate the "dead_strip" feature if objc binary stripping is enabled. - More stable naming scheme for lambda classes in desugared android code - Convert --use_action_cache to a regular option - Per-architecture dSYM binaries are now propagated by apple_binary's AppleDebugOutputsProvider. - Avoid factory methods when desugaring stateless lambdas for Android - desugar calls to Objects.requireNonNull(Object o) with o.getClass() for android - Add an --copy_bridges_from_classpath argument to android desugaring tool - Change how desugar finds desugared classes to have it working on Windows - Evaluation of commands on TargetsBelowDirectory patterns (e.g. //foo/...) matching packages that fail to load now report more detailed error messages in keep_going mode. - Allow to have several inputs and outputs - Repository context's execute() function can print stdout/stderr while running. To enable, pass quiet=False. - Bazel can now be built with a bundled version of the OpenJDK. This makes it possible to use Bazel on systems without a JDK, or where the installed JDK is too old. - The --jobs flag now defaults to "auto", which causes Bazel to use a reasonable degree of parallelism based on the local machine's capacity. - Bazel benchmark (perf.bazel.build) supports Java and Cpp targets. - no factory methods generated for lambda expressions on android - The Linux sandbox no longer changes the user to 'nobody' by default, instead the current user is used as is. The old behavior can be restored via the --sandbox_fake_username flag. - /tmp and /dev/shm are now writable by default inside the Linux sandbox. - Bazel can now use the process-wrapper + symlink tree based sandbox implementation in FreeBSD. - turn on --experimental_incremental_dexing_error_on_missed_jars by default. - All android_binarys are now signed with both Apk Signature V1 and V2. See https://source.android.com/security/apksigning/v2.html for more details. - Windows MSVC wrappers: Not filtering warning messages anymore, use --copt=-w and --host_copt=-w to suppress them. - A downloader bug was fixed that prevented RFC 7233 Range connection resumes from working with certain HTTP servers - Introduces experimental android_device rule for configuring and launching Android emulators. - For boolean flags, setting them to false using --no_<flag_name> is deprecated. Use --no<flag_name> without the underscore, or --<flag_name>=false instead. - Add --experimental_android_compress_java_resources flag to store java resources as compressed inside the APK. - Removed --experimental_use_jack_for_dexing and libname.jack output of android_library. - blaze canonicalize-flags now takes a --show_warnings flag - Changing --invocation_policy will no longer force a server restart. - Bazel now supports Android NDK14. - android_binary multidex should now work without additional flags. - Use action_config in crosstool for static library archiving, remove ar_flag. - new option for bazel canonicalize-flags, --canonicalize_policy - Use action_config in crosstool for static library archiving, remove ar_flag. - android_library exports_manifest now defaults to True. - Fix select condition intersections. - Adds a --override_repository option that takes a repository name and path. This forces Bazel to use the directory at that path for the repository. Example usage: `--override_repository=foo=/home/user/gitroot/foo`. - fix idempotency issue with desugaring lambdas in interface initializers for android - --experimental_android_use_singlejar_for_multidex is now a no-op and will eventually be removed. - Every local_repository now requires a WORKSPACE file. - Remove jack and jill attributes of the android_sdk rule. - Add Skylark stubs needed to remove sysroot from CppConfiguration. - Desugar try-with-resources so that this language feature is available to deveces with API level under 19. - The flag --worker_max_retries was removed. The WorkerSpawnStrategy no longer retries execution of failed Spawns, the reason being that this just masks compiler bugs and isn't done for any other execution strategy either. - Bazel will no longer gracefully restart workers that crashed / quit, instead this triggers a build failure. - All java resources are now compressed in android_binary APKs by default. - All java resources are now compressed in android_binary APKs by default. - android_ndk_repository now creates a cc_library (@androidndk//:cpufeatures) for the cpufeatures library that is bundled in the Android NDK. See https://developer.android.com/ndk/guides/cpu-features.html for more details. - 'output_groups' and 'instrumented_files' cannot be specified in DefaultInfo. - You can increase the CPU reservation for tests by adding a "cpu:<n>" (e.g. "cpu:4" for four cores) tag to their rule in a BUILD file. This can be used if tests would otherwise overwhelm your system if there's too much parallelism. - Deprecate use_singlejar_for_proguard_libraryjars and force behavior to always on.