mirror of
https://github.com/enso-org/enso.git
synced 2024-12-23 17:03:32 +03:00
c367e76e44
Closes #10476. # Important Notes Let's see what exactly fails on the CI and fix that then...
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
---
|
|
layout: developer-doc
|
|
title: Upgrading GraalVM
|
|
category: infrastructure
|
|
tags: [infrastructure, build, graalvm, graal, jvm]
|
|
order: 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`.
|
|
|
|
## 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`](../../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`](../../tools/ci/docker/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.
|