[
https://issues.apache.org/jira/browse/KAFKA-19654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Stojadinović updated KAFKA-19654:
---------------------------------------
Description:
(!) {*}Note{*}: this blocks Gradle upgrade from 8 to 9 (KAFKA-19174) - _Gradle
upgrade related stuff are done, but can't be merged due to CI build issues._
See here for more details:
[https://github.com/apache/kafka/pull/19513#issuecomment-3236158518]
Interestingly enough: only parsing fails (not tests) and on top of that it
happens for flaky/new matrix {*}_only_{*}.
_______________________________________________________________________________________________________________________________
{*}(i) Update{*}: after so many testing on Gradle upgrade PR
([https://github.com/apache/kafka/pull/19513]) I can confirm that something
strange is going on between GitHub Actions and Develocity instances.
Let me describe just a tip of the issues here; will use 'com.gradle.develocity'
plugin version as an example (and please keep in mind that no classes/test are
added or changed):
* Gradle 9/PR branch (with plugin version 3.19, i.e. trunk version): *parsing
step fails for JUnit reports* (for flaky/new jobs, as noted above);
* Gradle 8/trunk branch (with plugin version upgrade *only* - from 3.19 to
3.19.1): CI build ends up with this error: *upload build to Develocity fails*
(on) From where I see this solution for this issue should be drafted along
these lines:
- 'com.gradle.develocity' plugin version and configuration
- `com.gradle.common-custom-user-data-gradle-plugin` version
- github action `setup-gradle` version and configuration
[~mumrah] [~chia7712] I will create a separate PR and tag you there (it will
be a trunk-based PR, I do believe it will be easier to test/solve these issues
on a trunk level (and only then to apply Gradle upgrade).
was:
(!) {*}Note{*}: this blocks Gradle upgrade from 8 to 9 (KAFKA-19174) - _Gradle
upgrade related stuff are done, but can't be merged due to CI build issues._
See here for more details:
[https://github.com/apache/kafka/pull/19513#issuecomment-3236158518]
Interestingly enough: only parsing fails (not tests) and on top of that it
happens for flaky/new matrix {*}_only_{*}.
_______________________________________________________________________________________________________________________________
{*}(i) Update{*}: after so many testing on Gradle upgrade PR
([https://github.com/apache/kafka/pull/19513]) I can confirm that something
strange is going on between GitHub Actions and Develocity instances.
Let me describe just a tip of the issues here (I will use
'com.gradle.develocity' plugin version as an example):
* Gradle 9 PR/branch (with plugin version 3.19, i.e. trunk version): *parsing
step fails for JUnit reports* (for flaky/new jobs, as noted above)
* Gradle 8/trunk (with plugin version upgrade *only* - from 3.19 to 3.19.1):
CI build ends up with this error: *upload build to Develocity fails*
(on) From where I see this solution for this issue should be drafted along
these lines:
- 'com.gradle.develocity' plugin version and configuration
- `com.gradle.common-custom-user-data-gradle-plugin` version
- github action `setup-gradle` version and configuration
[~mumrah] [~chia7712] I will create a separate PR and tag you there (it will
be a trunk-based PR, I do believe it will be easier to test/solve these issues
on a trunk level (and only then to apply Gradle upgrade).
> GitHub Actions issues with Develocity (for both trunk/Gradle 8 and with
> attempted upgrade to Gradle 9)
> ------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-19654
> URL: https://issues.apache.org/jira/browse/KAFKA-19654
> Project: Kafka
> Issue Type: Bug
> Components: build
> Reporter: Dejan Stojadinović
> Priority: Major
> Labels: CI, CI/CD, GitHub, Github, Gradle, build, gradle
>
> (!) {*}Note{*}: this blocks Gradle upgrade from 8 to 9 (KAFKA-19174) -
> _Gradle upgrade related stuff are done, but can't be merged due to CI build
> issues._
> See here for more details:
> [https://github.com/apache/kafka/pull/19513#issuecomment-3236158518]
> Interestingly enough: only parsing fails (not tests) and on top of that it
> happens for flaky/new matrix {*}_only_{*}.
> _______________________________________________________________________________________________________________________________
> {*}(i) Update{*}: after so many testing on Gradle upgrade PR
> ([https://github.com/apache/kafka/pull/19513]) I can confirm that something
> strange is going on between GitHub Actions and Develocity instances.
> Let me describe just a tip of the issues here; will use
> 'com.gradle.develocity' plugin version as an example (and please keep in mind
> that no classes/test are added or changed):
> * Gradle 9/PR branch (with plugin version 3.19, i.e. trunk version):
> *parsing step fails for JUnit reports* (for flaky/new jobs, as noted above);
> * Gradle 8/trunk branch (with plugin version upgrade *only* - from 3.19 to
> 3.19.1): CI build ends up with this error: *upload build to Develocity fails*
> (on) From where I see this solution for this issue should be drafted along
> these lines:
> - 'com.gradle.develocity' plugin version and configuration
> - `com.gradle.common-custom-user-data-gradle-plugin` version
> - github action `setup-gradle` version and configuration
> [~mumrah] [~chia7712] I will create a separate PR and tag you there (it will
> be a trunk-based PR, I do believe it will be easier to test/solve these
> issues on a trunk level (and only then to apply Gradle upgrade).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
