commit | f4d58293c69e9359141576d2da88665dc63f2467 | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Tue Dec 19 10:31:03 2017 +0100 |
committer | László Csomor <laszlocsomor@google.com> | Tue Dec 19 10:31:03 2017 +0100 |
tree | 9b882f7b35af282218ca345a765dee998b4846f5 | |
parent | 43001a55ab2de3ec692561cf8d47524018c041c7 [diff] |
Release 0.9.0 (2017-12-19) 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.
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.