Closed jomarko closed 1 year ago
@yesamer wait, because I think this is still on progress :P
@yesamer yes, @pefernan is correct, this is still draft, work in progress, here is the current state ()
1.) in runtime-tools-dev-ui-webapp
we fixed missing colors and icons for html
and tsx
form editor (so we have a progress, yay!)
2.) in runtime-tools-quarkus-extension-deployment
is the situation still the same
About the second point, it is for sure related to copying assets to some path, we do not know proper path, from my work, I do not think all assets can be copied to the same path
My plan is to:
1.) keep runtime-tools-quarkus-extension-deployment
in the same broken state as it is currently, but remove duplicated files, do simple exercise, grep -name envelope.js
it will return three copies on my machine, I believe only dev-static/webapp/envelope.js
is needed
2.) once we minify files copied from runtime-tools-dev-ui-webapp
, lets try to find their proper placement for runtime-tools-quarkus-extension-deployment
@yesamer @pefernan hi, let me share the status
1.) in runtime-tools-dev-ui-webapp
we fixed now colors and fonts
2.) in runtime-tools-quarkus-extension-deployment
is the situation still the same, I just decreased quite amount of files we copy from runtime-tools-dev-ui-webapp
into runtime-tools-quarkus-extension-deployment
, however changes in runtime-tools-quarkus-extension-deployment/pom.xml
are not final .
About the second point, I tried to summarize our issue on quarkus zulip topic https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/loading.20static.20resources
The code we use in https://github.com/apache/incubator-kie-kogito-apps/blob/main/runtime-tools-quarkus-extension-parent/runtime-tools-quarkus-extension-deployment/src/main/java/org/kie/kogito/runtime/tools/quarkus/extension/deployment/DevConsoleProcessor.java#L58 is deprecated, if you check in IDE and seems quite different from documented BuildStep
here https://quarkus.io/guides/writing-extensions#extension-defined-endpoints
What is your suggestion please?
PR job #8
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1885/8/display/redirect
Test results:
Those are the test failures:
PR job #11
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1885/11/display/redirect
Test results:
Those are the test failures:
PR job #1
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/test/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1885/1/display/redirect
Test results:
Those are the test failures:
PR job #12
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1885/12/display/redirect
Test results:
Those are the test failures:
PR job #13
was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-1885/13/display/redirect
Test results:
Those are the test failures:
@pefernan We can merge it after your approval, failing tests are unrelated.
@yesamer already approved.. please go ahead!
Partially closes kiegroup/kie-issues#527
Because the mentioned ticket affects two modules:
This PR fix the
runtime-tools-dev-ui-webapp
, howeverruntime-tools-quarkus-extension-deployment
still needs to be addressed.Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:
KOGITO-XYZ Subject
[0.9.x] KOGITO-XYZ Subject
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use [build-chain tool](https://github.com/kiegroup/github-action-build-chain) to handle cross repository builds and be sure that we always use latest version of the code for each repository. [build-chain tool](https://github.com/kiegroup/github-action-build-chain) is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See [local execution](https://github.com/kiegroup/github-action-build-chain#local-execution) details to get more information about it.How to retest this PR or trigger a specific build:
- for pull request checks Please add comment: Jenkins retest this - for a specific pull request check Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] tests - for quarkus branch checks Run checks against Quarkus current used branch Please add comment: Jenkins run quarkus-branch - for a quarkus branch specific check Run checks against Quarkus current used branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-branch - for quarkus main checks Run checks against Quarkus main branch Please add comment: Jenkins run quarkus-main - for a specific quarkus main check Run checks against Quarkus main branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-main - for quarkus lts checks Run checks against Quarkus lts branch Please add comment: Jenkins run quarkus-lts - for a specific quarkus lts check Run checks against Quarkus lts branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] quarkus-lts - for native checks Run native checks Please add comment: Jenkins run native - for a specific native check Run native checks Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] native - for native lts checks Run native checks against quarkus lts branch Please add comment: Jenkins run native-lts - for a specific native lts check Run native checks against quarkus lts branch Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] native-ltsHow to backport a pull request to a different branch?
In order to automatically create a **backporting pull request** please add one or more labels having the following format `backport-Quarkus-3 PR check is failing ... what to do ?
The Quarkus 3 check is applying patches from the `.ci/environments/quarkus-3/patches`. The first patch, called `0001_before_sh.patch`, is generated from Openrewrite `.ci/environments/quarkus-3/quarkus3.yml` recipe. The patch is created to speed up the check. But it may be that some changes in the PR broke this patch. No panic, there is an easy way to regenerate it. You just need to comment on the PR: ``` jenkins rewrite quarkus-3 ``` and it should, after some minutes (~20/30min) apply a commit on the PR with the patch regenerated. Other patches were generated manually. If any of it fails, you will need to manually update it... and push your changes.