jetbrains: fix JRE configuration for devcontainer development #297695
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
Jetbrains IDEs download the remote client GUI on each invocation. This client is not patched for Nix and includes its own JDK. JDK selection can be overridden through environment variable (to a Nix patched version).
Previously this was done with
JETBRAINSCLIENT_JDK
, now it should be done withJETBRAINS_CLIENT_JDK
.See previous PR #195132.
Without this change when trying to start a devcontainer session with either IntelliJ Ultimate or Jetbrains Gateway fails due to attempting to invoke the internally bundled JRE.
Things done
Set
JETBRAINS_CLIENT_JDK
in addition toJETBRAINSCLIENT_JDK
to preserve inconsistent behaviour of downloaded clients.Manually tested with the following environment:
Checked that IntelliJ Ultimate and Jetbrains Gateway is able to start a devcontainer for the Jetbrains sample project and author's own Go based projects.
Using following script to check environment variables were set as expected: