Hello, Getting this error on our CI/CD machine. `...

# gradle

[Elka]

Hello,
Getting this error on our CI/CD machine.

An exception occurred applying plugin request [id: 'org.jetbrains.kotlin.multiplatform', version: '1.9.22']
> Failed to apply plugin 'org.jetbrains.kotlin.multiplatform'.
   > Could not create an instance of type org.jetbrains.kotlin.gradle.plugin.internal.CustomPropertiesFileValueSource$Parameters.
      > org/jetbrains/kotlin/gradle/plugin/internal/CustomPropertiesFileValueSource

Could not create provider for value source CustomPropertiesFileValueSource.

Caused by: org.gradle.api.GradleException: Could not create provider for value source CustomPropertiesFileValueSource.

Caused by: org.gradle.api.reflect.ObjectInstantiationException: Could not create an instance of type org.jetbrains.kotlin.gradle.plugin.internal.CustomPropertiesFileValueSource$Parameters.

Caused by: java.lang.NoClassDefFoundError: org/jetbrains/kotlin/gradle/plugin/internal/CustomPropertiesFileValueSource

Environment:
Gradle 8.2 / Kotlin 1.9.22 / JDK openjdk 20.0.1 2023-04-18

Any help is appreciated!!

[Anton Lakotka [JB]]

Can you share more details of your setup (buildscripts) or share a reproducer project?

[Elka]

It is working on my machine, the CI/CD is on premise managed by IT. the same code base used to work and suddenly stopped working on CI/CD.
I was now thinking of clearning the ~/.gradle/caches.
Do you this would help?

[tapchicoma]

could you share Gradle build scan with error?

[Elka]

@tapchicoma which command exactly you want?

[tapchicoma]

add --scan option to command line on CI

[CLOVIS]

+ you'll have to accept the ToS

[CLOVIS]

you can take inspiration from this (it goes into settings.gradle.kts)

[CLOVIS]

(if you want to use it as-is, the plugin ID is dev.opensavvy.conventions.settings.enterprise)

[Elka]

okay deal

[CLOVIS]

you just have to create the environment variable instead of setting up everything

[Elka]

the weird part is the same code base used to work the day before, I am afraid of some interaction with other builds that could be running on that machine and that caused some inconsistency in the caches
As I shared earlier it’s on premise machine with Jenkins that builds multiple projects