chia7712 commented on PR #18539:
URL: https://github.com/apache/kafka/pull/18539#issuecomment-2613710671
@clayburn thanks for your response and explanation!
--
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
mumrah merged PR #18539:
URL: https://github.com/apache/kafka/pull/18539
--
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: jira-unsubscr...@kafka.apache.o
clayburn commented on PR #18539:
URL: https://github.com/apache/kafka/pull/18539#issuecomment-2605233411
I think it is because you triggered those via workflow dispatch, when really
the CI Complete workflow needs to have a corresponding run of the CI workflow.
Without that corresponding run
chia7712 commented on PR #18539:
URL: https://github.com/apache/kafka/pull/18539#issuecomment-2604574551
merge trunk and upgrade the plugin to 3.19
@clayburn do you have any idea that the publish task always say there is no
previous data? I don't dig in it, but other PRs don't encount
chia7712 commented on PR #18539:
URL: https://github.com/apache/kafka/pull/18539#issuecomment-2603152098
merge trunk to run QA again
--
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 c
mimaison commented on PR #18539:
URL: https://github.com/apache/kafka/pull/18539#issuecomment-2598139400
@chia7712 Can we merge this?
--
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
clayburn opened a new pull request, #18539:
URL: https://github.com/apache/kafka/pull/18539
This PR migrates the Kafka project to publish Build Scans to the the new
Develocity instance at develocity.apache.org.
https://issues.apache.org/jira/browse/KAFKA-18454
*More detailed de
