-
Notifications
You must be signed in to change notification settings - Fork 59
add JDK 12 community build #862
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
using
|
went to https://scala-ci.typesafe.com/view/scala-2.12.x/newJob and cloned the scala-2.12.x-jdk11-integrate-community-build job to scala-2.12.x-jdk12-integrate-community-build , changing jvmVersion to 12 and assigning it to behemoth 1 https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-jdk12-integrate-community-build/
note to self: do this for 2.13 too, but I'll probably want to get the whole 2.12 build extracting first |
darn those third-party libraries and their flaky builds! oh, wait... who, us?
|
everything extracts now except:
I'll have to come back to this. |
outside of dbuild, if I build scala-java8-compat on JDK 12, it works fine. I see back in the community build context, I note that in scala-java8-compat, EDIT: scala/scala-java8-compat#131 should fix it |
everything extracts now 🎉 we can track further progress at #796 |
|
in the first runs, 98 projects are green. that's encouraging, it means nothing catastrophic is wrong. about 10 projects fail that didn’t fail on JDK 11. I’ll gradually investigate them. usually it’s just that some silly thing in the build isn’t expecting a “12”. occasionally it’s something more substantial |
now tracking any further progress at #796 |
JDK 12 "overall feature set is frozen" (according to https://openjdk.java.net/projects/jdk/12/) as of Feb 13 2019)
we might as well install an early-access JDK 12 build and try it, see what happens, perhaps it will turn up something we ought to do something about
ea builds are here: https://jdk.java.net/12/
behemoth 1 has the lightest community build load at present
The text was updated successfully, but these errors were encountered: