Closed github-actions[bot] closed 1 year ago
There were some findings before, let's check if they persist: https://github.com/gradle/ide-smoke-tests/issues/83
Detailed version:
Welcome to Gradle 8.5-20230904225832+0000!
------------------------------------------------------------
Gradle 8.5-20230904225832+0000
------------------------------------------------------------
Build time: 2023-09-04 22:58:32 UTC
Revision: 182174e4d1f56b534bdbd87a98d7eae248ac2520
Kotlin: 1.9.10
Groovy: 3.0.17
Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM: 17.0.8.1 (Eclipse Adoptium 17.0.8.1+1)
OS: Mac OS X 13.5.1 aarch64
IntelliJ IDEA 2023.2.1 (Ultimate Edition)
Build #IU-232.9559.62, built on August 23, 2023
Runtime version: 17.0.8+7-b1000.8 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.1
GC: G1 Young Generation, G1 Old Generation
Note: IDEA EAP == IDEA stable, we are after release
Not done
Test Plan
1. Set up local test environment
for sample in $(ls | grep -e '^[0-9][0-9].*'); do cd $sample; ./gradlew wrapper --gradle-version nightly; cd -; done
git clean -fdx
to remove build artifacts from all sample projectsANDROID_HOME
environment variable is properly set on you machine03-multiproject
JDK 17 is used (Spring Boot plugin requirement)2. Document components
gradle --version
3. Verify scenarios
These scenarios are automatically generated from the lines starting with
TODO (scenario)
in the build script and code files.The sample projects are located in the numbered folders in the repository root. For each project, follow the steps below:
In case of a failure:
// Known issue: https://youtrack.jetbrains.com/issue/IDEA-123456
Scenarios in
build-src
Scenarios in
included-build-src
Scenarios in
multiproject
Scenarios in
java-build-src
Scenarios in
version-catalog-build-src
Scenarios in
error-in-build-script
Scenarios in
test-launcher
4. Finalize
Known issue
reference from the sources.new-regresssion-reported
label if you reported something to JetBrains