mirror of
https://github.com/enso-org/enso.git
synced 2024-12-25 03:22:43 +03:00
c367e76e44
Closes #10476. # Important Notes Let's see what exactly fails on the CI and fix that then...
1.3 KiB
1.3 KiB
layout | title | category | tags | order | |||||
---|---|---|---|---|---|---|---|---|---|
developer-doc | Upgrading GraalVM | infrastructure |
|
5 |
Upgrading GraalVM
After upgrading the project to a newer version of GraalVM, all developers must take the following actions to be able to continue development after the upgrade:
- Download the new JVM version and set it as the default for the project. If you use IntelliJ, you will also need to update the JVM used for the project in the project settings.
- Re-run
sbt bootstrap
to get the updated Truffle JAR (if there are issues updating, removingengine/runtime/build-cache
directory may help). - Do a full clean (it may not always be required, but not doing it often
leads to problems so it is much safer to do it) by running
enso/clean
.
Upgrading the Build
If you are upgrading the build to a new GraalVM version, you additionally need to perform the following tasks:
- Change the expected GraalVM version in the
build.sbt
configuration. This is both a version number and (if it is changed), the associated version of Java. - Change the base image in the
Dockerfile
to contain the correct GraalVM version. - Just to be sure, search for the version regex in all the files in the repo.
- Ensure that all deprecations have been handled.