Skip to content
Latchkey

Kotlin "Could not resolve org.jetbrains.kotlin" in CI

Gradle could not download a Kotlin module (stdlib, plugin, or compiler) from the configured repositories. The version does not exist, the repository is missing, or the network blocked the fetch.

What this error means

The build fails during resolution with "Could not resolve org.jetbrains.kotlin:kotlin-stdlib:<version>" or "Could not resolve all artifacts for configuration", naming the Kotlin coordinate.

kotlin
> Could not resolve org.jetbrains.kotlin:kotlin-stdlib:2.99.0.
  > Could not find org.jetbrains.kotlin:kotlin-stdlib:2.99.0.
    Searched in the following locations:
      - https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/...

Common causes

The requested Kotlin version does not exist

A typo or a not-yet-published version means no repository has that kotlin-stdlib or plugin artifact.

A required repository is not declared

The Kotlin artifact lives in a repository (Gradle Plugin Portal, Maven Central) the build did not add, so resolution finds nothing.

How to fix it

Pin a published Kotlin version

  1. Read the coordinate and version in the "Could not find" line.
  2. Set the Kotlin plugin and stdlib to a real released version.
  3. Re-run so the artifact resolves.
build.gradle.kts
plugins {
    kotlin("jvm") version "2.0.0"
}

Declare the repositories

Ensure Maven Central and, for plugins, the Plugin Portal are configured so Kotlin artifacts can be found.

build.gradle.kts
repositories {
    mavenCentral()
}

How to prevent it

  • Use only Kotlin versions that are actually published.
  • Declare mavenCentral() and the Plugin Portal where needed.
  • Cache the Gradle dependency directory so transient fetch failures do not repeat.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →