| commit | 123f2b9ee929297cd35ea67ce3f9c4f29d84e4a3 | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Wed Feb 12 04:34:00 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 12 04:34:58 2020 -0800 |
| tree | 4e1ad70b632dd9a41f17047fc0b327287c0c905a | |
| parent | 146d51aa1ec9dcb721a7483479ef0b1ac21d39f1 [diff] |
Remove git notes usage from release process Previously we store release name, candidate number, cherry-picks and release notes info in git repo using `git notes`. To remove this complexity, we remove all git notes usage in this change. Instead of using git notes, we parse release name and candidate number from branch name or tag name. For cherry-picks, we rely on the git patch-id to find the original commit hash. And for release notes, there is no need to store it in git notes, because we always manually modify the generated release note. Closes #10741. PiperOrigin-RevId: 294639345
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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
