forked from bazelbuild/bazel
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added a blog post for the beta release
-- MOS_MIGRATED_REVID=102670969
- Loading branch information
Showing
1 changed file
with
46 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
--- | ||
layout: posts | ||
title: Bazel Builder Blasts Beyond Beta Barrier | ||
--- | ||
|
||
_Reposted from [Google's Open Source blog](http://google-opensource.blogspot.com/2015/09/building-build-system-bazel-reaches-beta.html)._ | ||
|
||
We're excited to announce the Beta release of [Bazel](http://bazel.io), an [open | ||
source](https://github.com/bazelbuild/bazel) build system designed to support a | ||
wide variety of different programming languages and platforms. | ||
|
||
There are lots of other build systems out there -- Maven, Gradle, Ant, Make, and | ||
CMake just to name a few. So what's special about Bazel? Bazel is what we use to | ||
build the large majority of software within Google. As such, it has been | ||
designed to handle build problems specific to Google's development environment, | ||
including a massive, shared code repository in which all software is built from | ||
source, a heavy emphasis on automated testing and release processes, and | ||
language and platform diversity. Bazel isn't right for every use case, but we | ||
believe that we're not the only ones facing these kinds of problems and we want | ||
to contribute what we've learned so far to the larger developer community. | ||
|
||
Our beta release provides: | ||
|
||
* Binary releases for | ||
[Linux and OS X](https://github.com/bazelbuild/bazel/releases). | ||
* Support for building and testing C++, Java, Python, Rust, | ||
[and more](http://bazel.io/docs/build-encyclopedia.html). | ||
* Support for building Docker images, Android apps, and iOS apps. | ||
* Support for using libraries from | ||
[Maven, GitHub, and more](http://bazel.io/docs/external.html). | ||
* [A robust API](http://bazel.io/docs/skylark/index.html) for adding your own | ||
build rules. | ||
|
||
Check out the [tutorial app](http://bazel.io/docs/tutorial/index.html) to see a | ||
working example using several languages. | ||
|
||
We still have a long way to go. Looking ahead towards our 1.0.0 release, we | ||
plan to provide Windows support, distributed caching, and Go support among other | ||
features. See our [roadmap](http://bazel.io/roadmap.html) for more details | ||
and follow our [blog](http://bazel.io/blog) or | ||
[Twitter](https://twitter.com/bazelbuild) account for regular updates. Feel | ||
free to contact us with questions or feedback on the | ||
[mailing list](https://groups.google.com/forum/#!forum/bazel-discuss) or IRC | ||
(#bazel on freenode). | ||
|
||
_By Jeff Cox, Bazel team_ |