Comments (8)
Creating rc1:
bazel commit hash: 1de8aa398434ffb2e5c97d35ba97a80ea70a79db
build: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/107
$ export COMMIT_HASH=1de8aa398434ffb2e5c97d35ba97a80ea70a79db
$ export JDK_VERSION=11
$ export NEW_VERSION=2.0
$ export RC=1
$ src/create_java_tools_release.sh --commit_hash $COMMIT_HASH --java_tools_version $NEW_VERSION --java_version $JDK_VERSION --rc $RC --release false
release_candidates/javac11/v2.0/java_tools_javac11_linux-v2.0-rc1.zip f70b20a9b8b53e85b00bc78d097663ea825ce58fc0824f4d9639e6e0156a3391
release_candidates/javac11/v2.0/java_tools_javac11_windows-v2.0-rc1.zip 8f3c20b8fb2253fc0e14ab72ab2156814f6f326d822937f08bdc89399017ce3d
release_candidates/javac11/v2.0/java_tools_javac11_darwin-v2.0-rc1.zip 898f4755287bd63c3c2c43442c5b69f94a1a350d2ece691de94d7d4e942df728
from java_tools.
Bazel upgrade is happening in bazelbuild/bazel#8498
Bazel tests pipeline started: https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/3129
from java_tools.
The tests fail due to a circular dependency:
ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/4608/execroot/io_bazel/_tmp/560d84240c3e286e5662ef42830cec54/_bazel_buildkite-agent/b67d64e301e5c5e87c5776aec07a8d26/external/bazel_tools/tools/jdk/BUILD:59:1: in java_toolchain_alias rule @bazel_tools//tools/jdk:current_java_toolchain: cycle in dependency graph:
//foo:gen
//bar:bar-java (host)
.-> @bazel_tools//tools/jdk:current_java_toolchain (host)
| @bazel_tools//tools/jdk:legacy_current_java_toolchain (host)
| @bazel_tools//tools/jdk:remote_toolchain (host)
| @remote_java_tools_linux//:toolchain (host)
| @remote_java_tools_linux//:jacoco_coverage_runner (host)
`-- @bazel_tools//tools/jdk:current_java_toolchain (host)
This requires a fix in bazel and a new rc.
from java_tools.
Fix was sent in bazelbuild/bazel#8529. A new RC can be created after bazelbuild/bazel#8529 is merged in bazel.
from java_tools.
Creating rc2:
bazel commit hash: 3dc59e400a9e0a57f34aa990ec410a1b2af760d3
build: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/108
$ export COMMIT_HASH=3dc59e400a9e0a57f34aa990ec410a1b2af760d3
$ export JDK_VERSION=11
$ export NEW_VERSION=2.0
$ export RC=2
$ src/create_java_tools_release.sh --commit_hash $COMMIT_HASH --java_tools_version $NEW_VERSION --java_version $JDK_VERSION --rc $RC --release false
release_candidates/javac11/v2.0/java_tools_javac11_linux-v2.0-rc2.zip ff35a39d943dd592368b0340480de0b22cd8792743b4289182fe0f6bb91d0355
release_candidates/javac11/v2.0/java_tools_javac11_windows-v2.0-rc2.zip f5268bd0ae88195c36f8dd8fc3eeae9b5ed83c122bde7c16d69cd8215d832620
release_candidates/javac11/v2.0/java_tools_javac11_darwin-v2.0-rc2.zip 5f285e710408a1d8ba5c08aac53f54b919c367cdb6fafc3c8f67573db6a9fa09
from java_tools.
Testing for rc2 failed with errors like these:
external/remote_java_tools_linux/java_tools/ijar/ijar: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by external/remote_java_tools_linux/java_tools/ijar/ijar)
This happened because the java tools Buildkite pipeline was recently updated by the EngProd team to build the linux artifact on Ubuntu 18 instead of Ubuntu 14.
I update the pipeline settings to build on Ubuntu 14 and created rc3:
bazel commit hash: 00b5dadc485f968bced9dc152d9f391a3dc1992b
build: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/111
$ export COMMIT_HASH=00b5dadc485f968bced9dc152d9f391a3dc1992b
$ export JDK_VERSION=11
$ export NEW_VERSION=2.0
$ export RC=3
$ src/create_java_tools_release.sh --commit_hash $COMMIT_HASH --java_tools_version $NEW_VERSION --java_version $JDK_VERSION --rc $RC --release false
release_candidates/javac11/v2.0/java_tools_javac11_linux-v2.0-rc3.zip 5714c0a34c99b5a474b281c5e0f2019c8a24594a8288062dc307faefd1738fac
release_candidates/javac11/v2.0/java_tools_javac11_windows-v2.0-rc3.zip ff5f13b93a048518f7263932d5a26d60c4d56d0a969cf8b226015bc85dedb57d
release_candidates/javac11/v2.0/java_tools_javac11_darwin-v2.0-rc3.zip b94f14d0b1d491da988af1f2f63abe1fee42a880d7e8ca666a1df4a1e03ba37a
from java_tools.
My change in the buildkite pipeline settings was not enough to build on Ubuntu 14. I sent a PR to change this setting in the pipeline yml configuration file as well (bazelbuild/continuous-integration#695)
New build for RC 4: https://buildkite.com/bazel-trusted/java-tools-binaries-java/builds/113
bazel commit hash: 50c876e337a6e40ade7069d46649ae71296cfc14
$ export COMMIT_HASH=50c876e337a6e40ade7069d46649ae71296cfc14
$ export JDK_VERSION=11
$ export NEW_VERSION=2.0
$ export RC=4
$ src/create_java_tools_release.sh --commit_hash $COMMIT_HASH --java_tools_version $NEW_VERSION --java_version $JDK_VERSION --rc $RC --release false
release_candidates/javac11/v2.0/java_tools_javac11_linux-v2.0-rc4.zip 074d624fb34441df369afdfd454e75dba821d5d54932fcfee5ba598d17dc1b99
release_candidates/javac11/v2.0/java_tools_javac11_windows-v2.0-rc4.zip 2c3fc0ce7d30d60e26f4b8a36e2eadcf9e6a9d5a51b667d3d13b78db53b24251
release_candidates/javac11/v2.0/java_tools_javac11_darwin-v2.0-rc4.zip 0ceb0c9ff91256fe33508306bc9cd9e188dcca38df78e70839d426bdaef67a38
from java_tools.
All tests passed. Releasing RC4:
$ export JDK_VERSION=11
$ export NEW_VERSION=2.0
$ export RC=4
$ src/create_java_tools_release.sh --java_tools_version $NEW_VERSION --java_version $JDK_VERSION --rc $RC --release true
releases/javac11/v2.0/java_tools_javac11_linux-v2.0.zip 074d624fb34441df369afdfd454e75dba821d5d54932fcfee5ba598d17dc1b99
releases/javac11/v2.0/java_tools_javac11_windows-v2.0.zip 2c3fc0ce7d30d60e26f4b8a36e2eadcf9e6a9d5a51b667d3d13b78db53b24251
releases/javac11/v2.0/java_tools_javac11_darwin-v2.0.zip 0ceb0c9ff91256fe33508306bc9cd9e188dcca38df78e70839d426bdaef67a38
from java_tools.
Related Issues (20)
- Release: java_tools v11.10 HOT 9
- Release: java_tools v11.11 HOT 5
- Release: java_tools v11.12 HOT 1
- Release: java_tools v11.12 HOT 6
- java_tools 12.0 HOT 9
- [bzlmod] How can it be used by MODULE.bazel HOT 1
- Release: java_tools v12.1 HOT 10
- Release: java_tools v12.2 HOT 6
- Release: java_tools v12.3 HOT 6
- Release: java_tools v12.4 HOT 17
- Release: java_tools v12.5 HOT 8
- Release: java_tools v12.6 HOT 8
- Release: java_tools v12.7 HOT 11
- Release: java_tools v12.8 HOT 10
- Release: java_tools v13.0 HOT 9
- Release: java_tools v13.1.0 HOT 3
- Release: java_tools v13.2.0 HOT 2
- Release: java_tools v13.3 HOT 10
- Release: java_tools v13.4.0 HOT 17
- Release: java_tools v13.5.0 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from java_tools.