Bazel: Release 3.2 - May 2020

[laurentlb]

Cut date: 2020-05-04

[philwo]

Status of Bazel 3.2.0

• Target baseline: 1d93d26d9900328dcba0026bf21cb45cc37a4596
• Expected release date: 2020-05-18
• List of release blockers

To report a release-blocking bug, please file a bug using the Release blocker label, and cc me.

Task list:

• [x] Update GitHub issues for incompatible changes
• [X] Pick release baseline: 1d93d26d9900328dcba0026bf21cb45cc37a4596
• [x] Create release candidate: https://releases.bazel.build/3.2.0/rc1/index.html
• [x] Check downstream projects: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1485
• [x] [Create draft release announcement](https://docs.google.com/document/d/1wDvulLlj4NAlPZamdlEVFORks3YXJonCjyuQMUQEmB0/edit)
• [x] Send for review the release announcement PR:
• [ ] Push the release, notify package maintainers:
• [ ] Update the documentation
• [ ] Push the blog post
• [ ] Update the release page

[philwo]

Pushed 3.2.0rc1:

RELEASE_NUMBER=3.2.0
BASELINE_COMMIT=1d93d26d9900328dcba0026bf21cb45cc37a4596
git clone https://github.com/bazelbuild/bazel.git ~/bazel-release-$RELEASE_NUMBER
cd ~/bazel-release-$RELEASE_NUMBER
scripts/release/release.sh create $RELEASE_NUMBER $BASELINE_COMMIT
scripts/release/release.sh push

[ifoox]

Any updates?

[philwo]

I'm not aware of any release blockers or complaints. I think we can release it tomorrow. :)

[philwo]

Bazel 3.2.0 has been pushed! 🚀

Pinging package maintainers @vbatts @petemounce @excitoon @chenrui333.

[chenrui333]

Upgraded to latest Bazel in https://github.com/Homebrew/homebrew-core/pull/55354

[konste]

@philwo We were specifically waiting for 3.2.0 for the flag --experimental_windows_watchfs but when we try to use it we get "ERROR: Unrecognized option: --experimental_windows_watchfs". Is it possible that 11334 somehow did not make it to 3.2.0?

[benjaminp]

3.2.0 was branched at the beginning of the month thus excluding 33106877277e6bfb3944b5b65b5d700fb781764e.

[konste]

@benjaminp Thank you for the explanation!

[philwo]

@konste Bazel 3.3.0rc1 should be cut beginning of next week, so you can test it using that version then :)

[vbatts]

late to the party, but fedora and centos are built https://copr.fedorainfracloud.org/coprs/vbatts/bazel/build/1424821/
Still epel-7-aarch64 failed, but all the rest succeeded.

[philwo]

Thank you @vbatts 😊 I'll have a look at the epel7-aarch64 failure. Bazel "should" work on that platform...

[philwo]

+ env ./compile.sh
Building Bazel from scratcherror: Bad exit status from /var/tmp/rpm-tmp.pj9GrC (%build)
    Bad exit status from /var/tmp/rpm-tmp.pj9GrC (%build)
RPM build errors:
Child return code was: 1

@vbatts It's strange that the compile.sh command doesn't print any error and just exits with code 1 after printing Building Bazel from scratch. I currently don't have a CentOS 7 machine on that platform available, but if I have some time, I'll try to find out what's failing there.

[jiridanek]

@philwo I've filled https://github.com/vbatts/copr-build-bazel/issues/14 for the epel-7-aarch64 build failure.

[vbatts]

I welcome any testing that folks offer here :-D

[limdor]

What is the status? Is there any reason why this issue is not closed? Just asking before starting the process to upgrade to 3.2.

[philwo]

@limdor No reason, I think we just forgot to close it. 😊