Skip to content

chore(jetbrains): migrate to stable IntelliJ Gradle plugin - #11869

Merged
kirillk merged 2 commits into
mainfrom
slimy-principal
Jul 1, 2026
Merged

chore(jetbrains): migrate to stable IntelliJ Gradle plugin#11869
kirillk merged 2 commits into
mainfrom
slimy-principal

Conversation

@kirillk

@kirillk kirillk commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

What

  • Upgrade the JetBrains plugin to IntelliJ Platform Gradle Plugin 2.17.0 and remove the snapshot-only plugin resolution setup.
  • Let the Gradle plugin handle split-mode port selection with kilo.splitModeServerPort=0, and wire :runIdeSplitMode with the same local CLI prep as backend runs.
  • Replace the compound split-mode IDE run config with a direct :runIdeSplitMode Gradle config and refresh developer docs.

Why

This catches our JetBrains plugin development tooling up with the now-released IntelliJ Platform Gradle Plugin work from JetBrains/intellij-platform-gradle-plugin#2164. With 2.17.0 released, we can stop carrying the local random-port workaround and snapshot repository setup.

Notes

  • The checked-in run configs pass --no-configuration-cache because the IntelliJ run-IDE tasks still hit a configuration-cache serialization issue in this setup.
  • No changeset: this is development tooling only.

Validation

  • ./gradlew tasks --all
  • ./gradlew typecheck
  • ./gradlew --no-configuration-cache runIdeSplitMode --dry-run -Pkilo.splitModeServerPort=0 -Pkilo.dev.storage.isolated=true
  • bun turbo typecheck (pre-push)

Comment thread packages/kilo-jetbrains/README.md
@kilo-code-bot

kilo-code-bot Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The only change since the last review is a one-line documentation addition to packages/kilo-jetbrains/README.md explaining why the checked-in run configs pass --purge-old-log-directories — this resolves the previously open SUGGESTION on this PR.

Files Reviewed (1 file changed since last review)
  • packages/kilo-jetbrains/README.md
Previous Review Summary (commit 1285e54)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 1285e54)

Status: 1 Issue Found | Recommendation: Merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

SUGGESTION

File Line Issue
packages/kilo-jetbrains/README.md 112 New --purge-old-log-directories flag added to all three run configs isn't explained anywhere
Files Reviewed (10 files)
  • CONTRIBUTING.md
  • packages/kilo-docs/pages/contributing/architecture/jetbrains-plugin.md
  • packages/kilo-jetbrains/.run/Run IDE (Backend).run.xml
  • packages/kilo-jetbrains/.run/Run IDE (Frontend).run.xml
  • packages/kilo-jetbrains/.run/runIdeSplitMode.run.xml
  • packages/kilo-jetbrains/AGENTS.md
  • packages/kilo-jetbrains/README.md
  • packages/kilo-jetbrains/build.gradle.kts
  • packages/kilo-jetbrains/gradle/libs.versions.toml
  • packages/kilo-jetbrains/settings.gradle.kts

The build.gradle.kts port-selection logic, split-mode task wiring (runIdeFrontend/runIdeSplitMode), and the removed snapshot-repo/resolution-strategy in settings.gradle.kts all look correct and consistent with the stable 2.17.0 plugin migration described in the PR body. Docs (README.md, AGENTS.md, CONTRIBUTING.md, jetbrains-plugin.md) and the three .run/*.xml configs are updated consistently with each other.


Reviewed by claude-sonnet-5-20260630 · Input: 16 · Output: 2.9K · Cached: 357.7K

Review guidance: REVIEW.md from base branch main

@kirillk
kirillk merged commit 5f4c96b into main Jul 1, 2026
28 checks passed
@kirillk
kirillk deleted the slimy-principal branch July 1, 2026 19:23
t7tran pushed a commit to t7tran/kilocode that referenced this pull request Aug 14, 2026
chore(jetbrains): migrate to stable IntelliJ Gradle plugin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants