ci(jetbrains): include plugin build in typecheck

[kirillk]

Context

Run the JetBrains plugin build as part of the repo-wide typecheck path so the existing GitHub typecheck workflow catches JetBrains compile and packaging regressions on every CI run. The build also generates the Kotlin client from the current CLI OpenAPI output rather than relying on the tracked packages/sdk/openapi.json.

Also adds JetBrains Kotlin tests to the existing test workflow via bun turbo test:ci.

Implementation

Typecheck (typecheck.yml — bun turbo typecheck):

• packages/kilo-jetbrains/package.json — added "typecheck": "bun run build" so Turbo picks up the package.
• turbo.json — added @kilocode/kilo-jetbrains#typecheck depending on @kilocode/cli#build with empty outputs, so CI builds the CLI first then runs the JetBrains build.
• packages/kilo-jetbrains/backend/build.gradle.kts + new GenerateOpenApiSpecTask.kt — a custom Gradle task runs bun dev generate from packages/opencode/, captures stdout into backend/build/generated/openapi-spec/openapi.json, and openApiGenerate is pointed at that build-local file. packages/sdk/openapi.json is not touched. The Gradle up-to-date input is scoped to src/server/ only to avoid cache busting on unrelated dist//node_modules/ changes.

Tests (test.yml — bun turbo test:ci):

• packages/kilo-jetbrains/script/test-ci.ts — runs ./gradlew test --continue (all modules, never stops on failure), then merges per-module JUnit XML results into .artifacts/unit/junit.xml for the CI report uploader. Always exits 0 so test failures surface as report annotations rather than blocking the job.
• turbo.json — added @kilocode/kilo-jetbrains#test:ci depending on @kilocode/kilo-jetbrains#typecheck so tests run after the plugin is built.

No new workflow file is needed for either change.

CI Timing Impact

Job	Before	After	Delta
typecheck	~4m	~5m 33s	+~1m 30s
unit (linux)	~3m 35s	~14m 43s	+~11m (6m 35s tests + overhead)

Screenshots

before	after
JetBrains not in typecheck or test output	@kilocode/kilo-jetbrains:typecheck and @kilocode/kilo-jetbrains:test:ci run in CI

How to Test

• Run bun turbo typecheck --filter=@kilocode/kilo-jetbrains — confirm Gradle runs generateOpenApiSpec, openApiGenerate, fixGeneratedApi, and buildPlugin.
• Run bun turbo test:ci --filter=@kilocode/kilo-jetbrains — confirm Gradle runs all tests and .artifacts/unit/junit.xml is produced.
• Confirm git diff -- packages/sdk/openapi.json is empty after either run.

CI Results

typecheck — passed, 5m 33s. @kilocode/kilo-jetbrains:typecheck in scope, Gradle generateOpenApiSpec → openApiGenerate → buildPlugin all ran on the Linux runner.

unit (linux) — passed, 14m 43s. @kilocode/kilo-jetbrains:test:ci ran after typecheck; Gradle executed 892 tests across frontend and backend modules, collected 53 JUnit suites into .artifacts/unit/junit.xml. Pre-existing failures from main are visible in the unit results (linux) report check without blocking the job.

Get in Touch

Kilo Code team

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (incremental — new commits since b894f8d)

New files and changes in this incremental pass:

• packages/kilo-jetbrains/gradle/libs.versions.toml — IntelliJ Gradle plugin bumped from 2.14.0 → 2.16.0. Routine dependency upgrade, no logic changes.

Observations (not blocking)

• test-ci.ts always exits 0: pre-existing JetBrains test failures won't block CI. Intentional — documented in the PR description.
• resolvePlatform is recursive without a cycle guard. Safe because the parents map is only populated by register() at session creation time and the session model forbids self-referential parent IDs.

_{Reviewed by claude-sonnet-4.6 · incremental pass}

---

_{Reviewed by claude-sonnet-4.6 · 150,461 tokens}

_{Review guidance: REVIEW.md from base branch main}

[catrielmuller]

Check the test that are failing