enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-24 04:24:01 +03:00
Code Issues Projects Releases Wiki Activity
8e20fc66dc
enso/docs/infrastructure/upgrading-graalvm.md
Pavel Marek 3e8467c204
Update GraalVM to 22.3.1 (#5602) 
Updates the engine to GraalVM 22.3.1 version, which contains fixes for:
- Chrome inspector issues - 38eb3b5932

# Important Notes
- Update to GraalVM 22.3.1
- Remove host object wrapping workaround
2023-02-14 15:51:17 +00:00

1.7 KiB
Raw Blame History

layout title category tags order
developer-doc Upgrading GraalVM infrastructure
infrastructure
build
graalvm
graal
jvm
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:

  1. 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.
  2. Re-run sbt bootstrap to get the updated Truffle JAR (if there are issues updating, removing engine/runtime/build-cache directory may help).
  3. 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.
  4. To be able to build or run tests for the launcher project, Native Image for the new GraalVM version has to be installed, as it is not included by default. This can be done with <path-to-graal-home>/bin/gu install native-image.
    • If there are problems building the Native Image, removing engine/launcher/build-cache (which contains the downloaded musl package) may help.

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.