commit | 0274d5385ca077fba067b3a0615e9dc5567c408d | [log] [tgz] |
---|---|---|
author | ulfjack <ulfjack@google.com> | Mon Mar 25 08:35:13 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 25 08:37:03 2019 -0700 |
tree | 05f81a7aba1ff411d0767085b4c2cf57e9c27c37 | |
parent | 54d7d61db1b5261c826cafca42a6d5159974d7c3 [diff] |
Use version --nognu_format for the bootstrap test The SOURCE_DATE_EPOCH is put into the version data we bake into the binary as the build timestamp, which is only available in --nognu_format. This is in preparation for switching to --gnu_format by default. We should consider changing compile.sh to put in a more useful stamp than the current output, which is 'bazel 0.23.2- (@non-git)', but that's independent of this change. Note that current bazel version output looks like this: Build label: 0.22.0 Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar Build time: Mon Jan 28 12:58:08 2019 (1548680288) Build timestamp: 1548680288 Build timestamp as int: 1548680288 Progress on #3599. PiperOrigin-RevId: 240144880
{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.