Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2114111907
HI @mimaison what can we do to get this going, as there is no response in
the discussion.
--
This is an automated message from the Apache Git Service.
To respond to the message,
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2090390142
Hi @mimaison seems no discussion happening on the mailing list, Just a query
as per the reply on the jira issue which I raised as per the comment a
committer has access to enable
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2034128217
@divijvaidya can you also have a look at this once
https://lists.apache.org/thread/f3yj7o5nfskz1onr59kmodm73kvtsktk
--
This is an automated message from the Apache Git Service.
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2014393617
Yes I would have followed the same , I have started a discussing on dev list.
https://lists.apache.org/thread/f3yj7o5nfskz1onr59kmodm73kvtsktk
--
This is an automated message
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2012341540
Instead of directly asking Infra, I think asking on the dev list first might
have been better as suggested above.
--
This is an automated message from the Apache Git Service.
To
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2012193438
@mimaison can you have a loot at it once at the JIRA mentioned in previous
comment
--
This is an automated message from the Apache Git Service.
To respond to the message,
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2012071722
I have created a JIRA to have the new job configured
https://issues.apache.org/jira/browse/INFRA-25631
--
This is an automated message from the Apache Git Service.
To respond to
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2010007861
I don't think (at least don't know how) we can modify the jobs in Jenkins
directly. The jobs are automatically created via the Jenkinsfile in this
repository. I see some other Apache
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-2003833677
Hi @mimaison additional jenkinsfile for ppc64le has been added , also as per
my understanding some changes would be required at
https://ci-builds.apache.org/job/Kafka/job/kafka/
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1983537805
Yeah that seems like the next best approach. However I have no idea how to
set that up. If you know how to set that up, go ahead and update the PR
otherwise you'll probably will have to
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1983520711
Thanks @mimaison for looking into at, so seems we are out of options to
build the specific stage daily, what if we add an additional jenkins file just
to build for ppc64le
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1983268003
Sorry for the delay. I tried building your branch and it fails with:
```
Scripts not permitted to use method
org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1971535782
@mimaison any updates?
--
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
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1490885160
##
Jenkinsfile:
##
@@ -174,6 +183,28 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
mimaison commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1481254113
##
Jenkinsfile:
##
@@ -174,6 +183,28 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1474755853
##
Jenkinsfile:
##
@@ -174,6 +183,28 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1474754259
##
Jenkinsfile:
##
@@ -1,3 +1,7 @@
+
+
+
+
Review Comment:
done
--
This is an automated message from the Apache Git Service.
To respond to the message,
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1474755853
##
Jenkinsfile:
##
@@ -174,6 +183,28 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
mimaison commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1474685305
##
Jenkinsfile:
##
@@ -174,6 +183,28 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1917302430
Hi @mimaison the above error was fixed.
--
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
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1877357358
Sorry for the delay. I tried to build this but it fails in the CI with the
following error:
```
WorkflowScript: 91: unexpected token: % @ line 91, column 82.
InMillis() /
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1869973402
Hi Team , any updates on the plan to merge this PR?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1833413348
Hi @mimaison any updates on the latest changes?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1815173826
JIRA ticket for Scala Installation on shared power nodes:
https://issues.apache.org/jira/browse/INFRA-25163
--
This is an automated message from the Apache Git Service.
To
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1815159323
Hi @mimaison I ran the `kafka.zk.ZkMigrationIntegrationTest` locally and all
the related tests are passing.
```
./gradlew -PscalaVersion=2.13.12 core:test --tests
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392404934
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392404934
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392309926
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392309926
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392307654
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
Vaibhav-Nazare commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392307654
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
mimaison commented on code in PR #13817:
URL: https://github.com/apache/kafka/pull/13817#discussion_r1392208754
##
Jenkinsfile:
##
@@ -174,6 +174,25 @@ pipeline {
echo 'Skipping Kafka Streams archetype test for Java 21'
}
}
+
+
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1807746432
Rerunning the build:
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-14717/2/pipeline/14/
--
This is an automated message from the Apache Git
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1807487012
Hi @mimaison Can we rerun the job now, jdk_21_latest has been installed on
the shared power nodes by ASF infra.
--
This is an automated message from the Apache Git Service.
To
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1802353727
Raised a JIRA ticket to have jdk_21_latest installed on shared power nodes
https://issues.apache.org/jira/browse/INFRA-25149
--
This is an automated message from the Apache
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1802275265
So obvious reasons, changes in Jenkinsfile are only tested if the PR is from
a committer. So I opened https://github.com/apache/kafka/pull/14717 to run your
changes.
You can see
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1802230356
Thanks for the updates! Can we switch to jdk_21_latest? as it's the newest
java version we use in the other stages
--
This is an automated message from the Apache Git Service.
To
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1759053190
Hi @mimaison I have updated the stage for PowerPC as of now, for the Java
Version upgrade I need to figure out how to do it, may be we can have it in
another PR?
--
This is an
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1757770296
Yes it would be better if the Java version can be specified as a config.
It's something you need to figure out.
The job will be automatically created when we commit the updated
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1757493253
@mimaison As my point of view for Java version , may be we can have this
part of config itself so we don't have to raise tickets frequently to ASF team,
wdyt?
--
This is an
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1757278411
Then I'd probably make the new ppc job copy the existing jobs and use a
single `stage`.
Another question: What will be the process of updating the Java version? Can
this be part
Vaibhav-Nazare commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1755428479
Hi @mimaison, thanks for the reply.
We were referring to older Jenkins file before the support was disabled on
Power, No specific reason to use nested stage fields.
If
mimaison commented on PR #13817:
URL: https://github.com/apache/kafka/pull/13817#issuecomment-1752766226
Thanks @Vaibhav-Nazare for the KP and PR.
I've not looked at Jenkinsfiles in a while, can you clarify why you used
nested `stage` fields unlike the other existing platforms?
--
43 matches
Mail list logo
