Update java_tools-release.yml (#2941)
Drop `venv` creation and `pip install`. That needs more packages to be
installed to work, instead we'll update the release process to not
require any additional packages.
<!--
Thank you for contributing to Bazel CI!
Before submitting a pull request, please read the contribution
guidelines:
https://github.com/bazelbuild/continuous-integration/blob/master/CONTRIBUTING.md
-->
### Issue description
<!--
Describe the problem, bug, or need this PR addresses.
If there is an existing issue, link it here (e.g. "Fixes #1234").
-->
### How this PR solves it
<!--
Provide a brief summary of the change and why this approach was chosen.
-->
### Testing
<!--
Describe how this change was verified (e.g. a Buildkite build link on
bazel-testing, or a local test run), or explain why testing is not
needed.
-->
diff --git a/pipelines/java_tools-release.yml b/pipelines/java_tools-release.yml
index c5c4a63..1d0fba8 100644
--- a/pipelines/java_tools-release.yml
+++ b/pipelines/java_tools-release.yml
@@ -50,9 +50,6 @@
echo "+++ Preparing release notes and .zip files"
cd scripts
- python3 -m venv venv
- source venv/bin/activate
- pip3 install wget
python3 release.py --artifacts "\$artifacts"
echo "+++ Downloading github-release"
