Don't create pip package in CI, it conflicts with newer versions of setuptools.

Author: arcra

.github/workflows/ci.yml

@@ -115,19 +115,6 @@ jobs:
           bazel test //tensorboard/summary/writer:event_file_writer_s3_test &&
           bazel test //tensorboard/compat/tensorflow_stub:gfile_fsspec_test &&
           bazel test //tensorboard/summary/writer:event_file_writer_fsspec_test
-      - name: 'Bazel: build Pip package (with TensorFlow only)'
-        if: matrix.tf_version_id == 'tf'
-        run: |
-          ./tensorboard/tools/update_version.sh
-          rm -rf /tmp/tb_nightly_pip_package && mkdir /tmp/tb_nightly_pip_package
-          bazel run //tensorboard/pip_package:build_pip_package -- /tmp/tb_nightly_pip_package
-      - name: 'Upload Pip package as an artifact (with TensorFlow only)'
-        # Prevent uploads when running on forks or non-master branch.
-        if: matrix.tf_version_id == 'tf' && github.repository == 'tensorflow/tensorboard' && github.ref == 'refs/heads/master'
-        uses: actions/upload-artifact@83fd05a356d7e2593de66fc9913b3002723633cb # v3.1.1
-        with:
-          name: tb-nightly
-          path: /tmp/tb_nightly_pip_package/*
 
   build-data-server-pip:
     runs-on: ${{ matrix.platform }}