[bazel] Update bazel to 0.17.1

[yongtang]

System information

• Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
• OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
• Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
• TensorFlow installed from (source or binary): source
• TensorFlow version (use command below): PR Add Apache Parquet support for TensorFlow Dataset #19461
• Python version: 2.7.12
• Bazel version (if compiling from source): 0.17.1/0.17.2
• GCC/Compiler version (if compiling from source): 5.4.0 20160609
• CUDA/cuDNN version: N/A
• GPU model and memory: N/A
• Exact command to reproduce: build of PR Add Apache Parquet support for TensorFlow Dataset #19461

Describe the problem

This is a placeholder for updating bazel to 0.17.1 so that PR #19461 could pass CI tests. Before bazel 0.17.1, bazel had some issues with fetching http_archive (See bazelbuild/bazel#5932). The issue has been fixed in 0.17.1.

The update of bazel 0.17.1 requires additional efforts than bumping versions in the repo (See #22281 (comment)). Pushing bleeding edge bazel immediately caused some issues before, so it is preferred to wait until a full release cycle before making the change.

At the moment, bazel 0.17.2 has been released (See bazelbuild/bazel#6164 (comment)) which is a minor release increment to 0.17.1.

/cc @gunan

Note The bazel 0.18.0 release is not far away (See bazelbuild/bazel#5963), as far as I could see. so wait until 0.18.0 is rebased, then update to 0.17.1 is also reasonable I think.

[gunan]

@av8ramit is currently updating the CI images to use bazel 0.17.

[av8ramit]

This will be done after the 1.11 release.

[yongtang]

@gunan @av8ramit Any update with bazel 0.17.1?

[av8ramit]

@yongtang We have not made the update yet due to some incompatibilities we are still working through.

[yongtang]

@av8ramit Thanks for the update! 👍 ❤️

[yongtang]

Looks like bazel 0.20 has been in place for tf repo: 55bbb4c

So this issue could be closed. Thanks all for the work!