mingyen066 opened a new pull request, #20795: URL: https://github.com/apache/kafka/pull/20795
Currently, if we merge to the 4.0 branch, the 4.0 `CI` workflow will be triggered. After the 4.0 `CI` completes, it triggeres the `ci-complete.yml` workflow in the "`trunk`" branch. However, the JDK versions and the names of the build scan files differ ([KAFKA-18748](https://issues.apache.org/jira/browse/KAFKA-18748)), so the `trunk` `ci-complete.yml` cannot find the correct build scan files that genereated by 4.0 `CI` workflow to upload to Develocity. To address this, I copied the relevant code from `ci-complete.yml` in 4.0 into the trunk workflow, allowing it to correctly find and upload the appropriate build scan archives. There is a potential issue with using Gradle 9 to upload Gradle 8 buildscan archives to Develocity, I am not sure if it will work because I don't have access to a Develocity server. I could only find the compatibility table for Develocity plugin and Gradle tools. https://docs.gradle.com/develocity/compatibility/#build_scans -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
