Started by user Pooja Ravi Running as SYSTEM [EnvInject] - Loading node environment variables. Building in workspace /home/jenkins/.jenkins/workspace/UstadMobile-primary2 The recommended git tool is: NONE No credentials specified > git rev-parse --resolve-git-dir /home/jenkins/.jenkins/workspace/UstadMobile-primary2/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/UstadMobile/UstadMobile.git # timeout=10 Fetching upstream changes from https://github.com/UstadMobile/UstadMobile.git > git --version # timeout=10 > git --version # 'git version 2.43.0' > git fetch --tags --force --progress -- https://github.com/UstadMobile/UstadMobile.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/primary^{commit} # timeout=10 Checking out Revision 5a159ae91682f6c40e3e81373dd83a8ad78674e6 (refs/remotes/origin/primary) > git config core.sparsecheckout # timeout=10 > git checkout -f 5a159ae91682f6c40e3e81373dd83a8ad78674e6 # timeout=10 Commit message: "Fix recording completion xAPI statements for ePUB and PDF." > git rev-list --no-walk 5a159ae91682f6c40e3e81373dd83a8ad78674e6 # timeout=10 [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content CONVEYOR_SITE_URL=https://devserver3.ustadmobile.com/conveyor/UstadMobile-primary2 ANDROID_SDK_ROOT=/var/lib/jenkins/Android/Sdk KEYSTORE=/var/lib/jenkins/javakey/android-release-keystore.properties ANDROID_HOME=/var/lib/jenkins/Android/Sdk [EnvInject] - Variables injected successfully. [Gradle] - Launching build. [UstadMobile-primary2] $ /home/jenkins/.jenkins/workspace/UstadMobile-primary2/gradlew -x app-android-baselineprofile:build -Pktorbundleproductionjs=true clean build > Configure project :app-android WARNING: The option setting 'android.defaults.buildfeatures.buildconfig=true' is deprecated. The current default is 'false'. It will be removed in version 10.0 of the Android Gradle plugin. To keep using this feature, add the following to your module-level build.gradle files: android.buildFeatures.buildConfig = true or from Android Studio, click: `Refactor` > `Migrate BuildConfig to Gradle Build Files`. > Configure project :app-react MR file generation for iOS is not supported on your system! w: The Default Kotlin Hierarchy Template was not applied to 'project ':app-react'': Explicit .dependsOn() edges were configured for the following source sets: [jsMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :core w: Please use `androidTarget` function instead of `android` to configure android target inside `kotlin { }` block. See the details here: https://kotl.in/android-target-dsl MR file generation for iOS is not supported on your system! w: Kotlin Multiplatform <-> Android Gradle Plugin compatibility issue: The applied Android Gradle Plugin version (8.9.0) is higher than the maximum known to the Kotlin Gradle Plugin. Tooling stability in such configuration isn't tested, please report encountered issues to https://kotl.in/issue" Minimum supported Android Gradle Plugin version: 7.0 Maximum tested Android Gradle Plugin version: 8.2 To suppress this message add 'kotlin.mpp.androidGradlePluginCompatibility.nowarn=true' to your gradle.properties w: The Default Kotlin Hierarchy Template was not applied to 'project ':core'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, commonJvmMain, jsMain, jvmMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :lib-cache w: The Default Kotlin Hierarchy Template was not applied to 'project ':lib-cache'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, commonJvmMain, jvmMain, jvmTest] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :lib-database w: The Default Kotlin Hierarchy Template was not applied to 'project ':lib-database'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, commonJvmMain, jvmMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template w: The Kotlin source set androidTest was configured but not added to any Kotlin compilation. You can add a source set to a target's compilation by connecting it with the compilation's default source set using 'dependsOn'. See https://kotl.in/connecting-source-sets > Configure project :lib-ihttp-core w: The Default Kotlin Hierarchy Template was not applied to 'project ':lib-ihttp-core'': Explicit .dependsOn() edges were configured for the following source sets: [jvmTest] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :lib-test-common w: Please use `androidTarget` function instead of `android` to configure android target inside `kotlin { }` block. See the details here: https://kotl.in/android-target-dsl w: The Default Kotlin Hierarchy Template was not applied to 'project ':lib-test-common'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, jvmMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :lib-ui-compose MR file generation for iOS is not supported on your system! w: The Default Kotlin Hierarchy Template was not applied to 'project ':lib-ui-compose'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, desktopMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :lib-util w: The Default Kotlin Hierarchy Template was not applied to 'project ':lib-util'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, jvmMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template > Configure project :sharedse w: Please use `androidTarget` function instead of `android` to configure android target inside `kotlin { }` block. See the details here: https://kotl.in/android-target-dsl w: The Default Kotlin Hierarchy Template was not applied to 'project ':sharedse'': Explicit .dependsOn() edges were configured for the following source sets: [androidMain, jvmMain] Consider removing dependsOn-calls or disabling the default template by adding 'kotlin.mpp.applyDefaultHierarchyTemplate=false' to your gradle.properties Learn more about hierarchy templates: https://kotl.in/hierarchy-template Configuration 'jsNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsTestNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsTestNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsTestNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. Configuration 'jsTestNpmAggregated' was resolved during configuration time. This is a build performance and scalability issue. See https://github.com/gradle/gradle/issues/2298 Run with --info for a stacktrace. [Incubating] Problems report is available at: file:///home/jenkins/.jenkins/workspace/UstadMobile-primary2/build/reports/problems/problems-report.html FAILURE: Build failed with an exception. * What went wrong: Gradle could not start your build. > Cannot create service of type TaskExecuter using method ProjectExecutionServices.createTaskExecuter() as there is a problem with parameter #9 of type ReservedFileSystemLocationRegistry. > Cannot create service of type ReservedFileSystemLocationRegistry using method ProjectExecutionServices.createReservedFileLocationRegistry() as there is a problem with parameter #1 of type List. > Could not create service of type ExecutionHistoryStore using ExecutionBuildServices.createExecutionHistoryStore(). > Cannot lock execution history cache (/home/jenkins/.jenkins/workspace/UstadMobile-primary2/.gradle/8.11.1/executionHistory) as it has already been locked by this process. * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.11.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD FAILED in 5s Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure Archiving artifacts Recording test results [Checks API] No suitable checks publisher found. [Slack Notifications] found #798 as previous completed, non-aborted build [Slack Notifications] will send OnEveryFailureNotification because build matches and user preferences allow it Finished: FAILURE