We are delighted to announce the 0.3.0 release of Bazel. This milestone is marked by support for IDE integration but also major features such as remote caching of build artifacts and experimental Windows support.
In this release, we made it possible to generate information for IDEs from Bazel build files using Skylark aspects.
Simultaneous with Bazel 0.3 release, we are announcing the availability of two projects integrating Bazel with different IDEs:
Bazel can now bootstrap on Windows without admin privilege and can use the Microsoft Visual C++ toolchain. Windows support is still highly experimental and we have identified several issues and their solutions. We are dedicated to a good native experience on Windows.
Alpha Lam has contributed experimental support for distributed caching and execution. This is an ongoing area of development and several engineers from Google are working with Alpha to enhance that support.
Remote repository rules can now be created using Skylark. This can be used to support your custom protocols, interfacing with new packaging systems or even do auto-configuration to use a toolchain on your local disk. We use it especially to have a better out-of-the-box experience with C++ toolchains.
--nolegacy_bazel_java_test
) is now the default.For changes since 0.2.3 (the minor version before 0.3.0), see the release notes for changes.
Looking ahead to 0.4.0:
--strategy=worker=Javac
will be resolved, making Java builds faster.A big thank you to our community for your continued support. Particular shout-outs to the following contributors:
Thank you all, keep the discussion and bug reports coming!