-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Quarkus version to 2.5.0.Final #1731
Conversation
The (build) optaweb-vehicle-routing check has failed. Please check the logs. |
The (build) optaplanner-quickstarts check has failed. Please check the logs. |
The (build) optaplanner check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
The (build) optaweb-employee-rostering check has failed. Please check the logs. |
The (build) kogito-examples check has failed. Please check the logs. |
The (build) kogito-runtimes check has failed. Please check the logs. |
The (build) optaplanner check has failed. Please check the logs. |
The (build) kogito-runtimes check has failed. Please check the logs. |
The (build) kogito-examples check has failed. Please check the logs. |
it looks like something broke in it looks like this line no longer generates the correct dep in the generated pom.xml:
instead of
which is correct on are you aware of this issue @ia3andy ? |
The (build) kogito-apps check has failed. Please check the logs. |
it looks like something changed in the GraphQL API @tiagodolphine @cristianonicolai for data index and job service |
This might be the reason: quarkusio/quarkus#20892 |
This is a tricky problem, removing the version from the builder call would make it fail to link the codestart, and having the version makes it alter the pom.xml The problem is on my end, I need to put my head around it. |
The (build) kogito-runtimes check has failed. Please check the logs. |
also @cristianonicolai is there any reason why the last number should be 1.0 in MonitoringIT ? expected 1.0 at the end:
but the log reads:
notice 0.0 at the end running seems correct
if we don't really care, I'd trim the "0.0" or "1.0" from the expected string for the time being... and maybe we should try and parse that line instead :P |
The (build) kogito-examples check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
it looks there is a similar issue for DRL and processes on Examples
|
The (build) kogito-runtimes check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
The (build) kogito-examples check has failed. Please check the logs. |
This is due to a regression for which I provided a PR on Quarkus core (quarkusio/quarkus#21562):
|
The (build) kogito-examples check has failed. Please check the logs. |
The (build) kogito-apps check has failed. Please check the logs. |
jenkins retest this |
The (build) kogito-apps check has failed. Please check the logs. |
Kudos, SonarCloud Quality Gate passed! |
jenkins rerun kogito-apps tests |
jenkins rerun kogito-apps tests |
Please review and merge
Related PRs: