Plugin for JetBrains Gateway enables local desktop development experience with the IntelliJ IDEs connected to OpenShift Dev Spaces.
We love to hear from users and developers.
You can ask questions, report bugs, and request features using GitHub issues in the Eclipse Che main repository.
- To test the plugin quickly against the Gateway instance bundled with the plugin, run:
./gradlew runIde- To skip opening the Gateway main window and connect to an already running workspace with the IDEA dev server:
./gradlew runIde --args="jetbrains-gateway://connect#type=devspaces&dwNamespace=john-che&dwName=my-ws"with replacing your DevWorkspace's namespace and name in dwNamespace and dwName parameters.
- Run:
./gradlew clean buildPlugin- Find the built plugin in the
build/distributionsfolder.
In the Gateway, click the gear button ⚙️, and choose Manage Providers to open the Plugins window.
There're a couple of options to install the plugin:
- Search for "OpenShift Dev Spaces".
- Click the gear button ⚙️ and choose
Install Plugin from Disk.... Then,- choose the built plugin (zip) located at the
build/distributionsfolder, or - download the plugin from the latest release
- choose the built plugin (zip) located at the
To check the plugin compatibility against the Gateway versions defined in the gradle.properties file.
./gradlew runPluginVerifier- To check the state of the port forwarding:
sudo lsof -i -P | grep LISTEN | grep 5990- The Gateway application and the Dev Spaces plugin logs are stored in
/Users/<USER_NAME>/Library/Logs/JetBrains/JetBrainsGateway<VERSION>/idea.log
- Find a draft release on the Releases page. The draft is created and updated automatically on each push to the
mainbranch. - Edit the draft:
- Click the
Generate release notesbutton and edit the release notes if needed - Click the
Publish releasebutton. The Release Workflow will attach the built plugin artifact to the published release.
- Click the
- Upload the plugin artifact to JetBrains Marketplace.
- Find the
Changelog update - v0.0.xPR, created automatically by the Release Workflow, and merge it. Note that currently, it requires closing and reopening the PR to trigger the PR checks. As, due to some issue, they are hanging in a waiting state forever. - Bump the
pluginVersionin the gradle.properties file.
Plugin based on the IntelliJ Platform Plugin Template.
