Skip to content

Automatically install JetBrains IDE plugins listed in devcontainer.json #1153

@dubinsky

Description

@dubinsky

Is your feature request related to a problem?

Yes: one of the advantages of using devpod and devcontainers is the ability to spin up pre-configured development environment for a repository; right now, while VSCode extensions needed can be described in the devcontainer.json file and installed automatically, JetBrains IDE plugins can not.

Which solution do you suggest?

After installing a JetBrains IDE, automatically install plugins listed in pre-determined location in the devcontainer.json file, for example:

"customizations" : {  
  "jetbrains" : {  
    "plugins" : ["org.intellij.scala"]
  }  
}

Which alternative solutions exist?
None that I know; my current work-around is:

Create a workspace, but do not start the IDE:

$ devpod up github.com/<user>/<workspace> --open-ide=false

Run the following script supplying the workspace name on the command line:

COMMAND="/home/vscode/.cache/JetBrains/RemoteDev/dist/intellij/bin/remote-dev-server.sh"  
PLUGINS="org.intellij.scala"  
devpod ssh $1 --command "$COMMAND installPlugins /workspaces/$1/ $PLUGINS"

(see: https://www.jetbrains.com/help/idea/work-inside-remote-project.html#plugins)

The command works, but results in:

Error tunneling to container: wait: remote command exited without exit status or exit signal

Start remote development in the workspace:

$ devpod up <workspace>

Additional context

Right now, after spinning up a workspace with code in - say - Scala with IntelliJ Idea, developer will either have to manually install the Scala plugin using the IDE's UI and restart the IDE or split the spin-up into three stages as in the work-around described above. Both approaches go against the spirit of devpod: start a fully configured development environment with one command (or one click); both require from the developer some additional actions and (even worse!) put on the developer some additional cognitive load needed to understand what those actions are.

Instead, all the actions required to obtain a working development environment should be automated and the decision what those actions are should reside in the code repository itself (side-by-side with the information on what tools have to be installed in the development environment).

It is true that the choice of the IDE to use belongs to the developer spinning up the workspace, but what plugins must be installed into the IDE chosen by the developer for it to be able to work with the code belong in the code.

As far as I understand, extensions to install in VSCode can indeed be listed in the devcontainer.json file; the same capability should exist for IntelliJ Idea.

Thank you!

P.S. There are some plugins that developer uses to customize the IDE (themes etc.); decision which plugins of this nature to install, regardless of the code repository underlying the workspace, does reside with the developer, and a facility to configure such plugins/extensions for automatic installation per IDE should be provided also (something like devpod ide set-options intellij -oPLUGINS="...").

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions