Hi all, We'd like to clarify some points for the migration.
1) Java version In the zulip chat, we discussed that we would like to use Java 17 for the minimal version for Quarkus 3.5.2 migration. https://kie.zulipchat.com/#narrow/stream/381961-drools-dev/topic/Quarkus.203.20migration/near/403922014 If we have Java 17 as the minimal version, we don't have to downgrade the quarkus-camel (3.0.0-M1 -> 2.15.0) and spring-boot (3.0.5 -> 2.6.6) versions. Do we agree on Java 17 as the minimal version? 2) Maven version This may not be very important. Quarkus 3.5.2 supports "[3.8.2,)" https://github.com/quarkusio/quarkus/blob/3.5.2/build-parent/pom.xml#L62 and recommneds "3.9.5" https://github.com/quarkusio/quarkus/blob/3.5.2/build-parent/pom.xml#L65 Probably "3.9.5" would be nice, but supportable versions would be fine. I just wanted to note here. 2) How to specify Java version in Jenkins CI (at the moment, for PR. But others too) Can we specify the Jenkins Java version at the kogito-runtimes side? Sorry, I'm not just knowledgeable about it. I tested "BUILD_JDK_TOOL" in `.ci/jenkins/Jenkinsfile`, but I cannot even confirm if it's effective. https://github.com/apache/incubator-kie-kogito-runtimes/pull/3292/files#diff-cc7fa003f07626ab6b3e955a24d87913c05aee8bb6c56fc05bf243f617fac962R21 Please kindly share the right way to specify that. 3) Spring Boot version Pere mentioned > my guts say that we should upgrade if we have the oportunity but I'm affraid it could add more pain. https://kie.zulipchat.com/#narrow/stream/381961-drools-dev/topic/Quarkus.203.20migration/near/403970518 Do we want to upgrade spring-boot higher than 3.0.5? Regards, Toshiya On Thu, Nov 23, 2023 at 6:36 PM Mario Fusco <[email protected]> wrote: > > It would be best to agree on a branch name - if it's quarkus3 - and > > generate special pipelines for that branch. So that we have clear > > separation. It would require branching of whole groups of repositories > > (similarly as above - incubator-kie-kogito-apps and others). > > Hi Jan, > > I agree on this. For now I replaced Toshiya's PR and now I have 2 PRs with > same branch name so CI could at least run against them, see: > > https://github.com/apache/incubator-kie-drools/pull/5589 > https://github.com/apache/incubator-kie-kogito-runtimes/pull/3291 > > CI is still running, anyway Drools should be ok (or if it isn't I will > take care of it), while kogito-runtimes is finally compiling, but locally I > have the 2 test failures that I'm pasting at the end of this email. I'm > working on them, but in all honest I have zero knowledge of that area, so I > would really appreciate any help on them. > > Thanks, > Mario > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-failsafe-plugin:3.1.2:verify > (integration-test) on project > kogito-quarkus-serverless-workflow-integration-test: There are test > failures. > > [ERROR] Failures: > [ERROR] EventTimedoutIT.testTimedout:94 > expected: 0L > but was: 1L > [ERROR] ForEachRestIT.testForEachSubflow:62 1 expectation failed. > Expected status code <201> but was <400>. > > [ERROR] Errors: > [ERROR] CallbackStateTimeoutsIT.callbackStateTimeoutsExceeded:60 » > ConditionTimeout Assertion condition defined as a > org.kie.kogito.test.utils.ProcessInstancesRESTTestUtils 1 expectation > failed. > Expected status code <404> but was <200>. > within 10 seconds. > [ERROR] > CallbackStateWithTimeoutsErrorHandlerIT.callbackStateTimeoutsExceeded:72 » > ConditionTimeout Assertion condition defined as a > org.kie.kogito.test.utils.ProcessInstancesRESTTestUtils 1 expectation > failed. > Expected status code <404> but was <200>. > within 10 seconds. > [INFO] > [ERROR] Tests run: 79, Failures: 2, Errors: 2, Skipped: 0 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
