Sync main branch with main-apache branch #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bump from 1.12.1 to .13.2 due to vulnerabilities: - https://security.snyk.io/package/npm/jquery-ui/1.12.1
apache#3242) * [KOGITO-9861] Fixing compilation issues with nested and arrays * [KOGITO-9861] Adding IT test
…e#3239) * [KOGITO-9844] Enhace jq validation to detect invalid functions * [KOGITO-9844] Improving function call
…pache#3240) - Ensures that the kogito-addons-quarkus-events-process addon produces the proper content type header when http cloud events are used. - Ensure the data index dev services produce the proper content type header.
* [KOGITO-9810] Supporting nested properties * Revert "[KOGITO-9810] Supporting nested properties" This reverts commit 8df264f. * [KOGITO-9810] Alternative approach * [KOGITO-9810] Fixing image test
…ervice-catalog as a dependency (apache#3249) This module is part of the kogito-runtimes project
* [kie-issues-249] Data index improvements * fix pojo it kafka dirty streams * fix mongodb debezium * fix for codecs registry * fix for mongodb publisher
* Timer node throws a TimerExpiredException in case there is an exception scope configured for it * Added standard header * Added IT for timeout with error handler * [KOGITO-9785] Implementing as error code * Removed new exception --------- Co-authored-by: Francisco Javier Tirado Sarti <ftirados@redhat.com>
…#3258) * kie-issues#647: add writeJunitReport to invoker configuration * Fix whitespace error --------- Co-authored-by: jstastny-cz <jan.stastny@ibm.com>
…resent in 1.22 (apache#3269)
* [KOGITO-9785] Handle event state error * [KOGITO-9785] Walters comments * Revert "[KOGITO-9785] Walters comments" This reverts commit 3d83f1c.
* [KOGITO-9811] Moving expression from ForEach to Process * [KOGITO-9811] Resolving timer on runtime * [KOGITO-9811] Improving message to include the expression possibility
… resolution (apache#3278) * kie-issues_680: Microprofile Config Service Catalog Addon throws exception at address resolution * Code review suggetions 1
…untime (apache#3252) * KOGITO-9886 Add the support for the ProcessDefinitionDataEvent at runtime
Co-authored-by: BAMOE CI <bamoe.ci@ibm.com>
apache#3277) * add UserTaskInstanceDataEvent to eventsAPIReflexion to fix data-index native integration test * updated file header to Licensed to the Apache Software Foundation
* Fix apache#3307 - Easier string interpolation As proposed in the issue description, remove the need for initial quoutes in case of string interpolation * Alternative implementation using optional
Co-authored-by: jstastny-cz <jan.stastny@ibm.com>
…che#3310) * KOGITO-9816 adding ProcessDefinitionRegistration to springboot
…addons-quarkus-microprofile-config-service-catalog (apache#3315)
rgdoliveira
requested review from
mareknovotny,
ricardozanini and
fantonangeli
ricardozanini
approved these changes
Dec 13, 2023
This was referenced Dec 13, 2023
fjtirado
approved these changes
Dec 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related PRs:
This PR includes all the changes done in main-apache branch and ignore any changes in .github and .ci folders
Many thanks for submitting your Pull Request ❤️!
Please make sure that your PR meets the following requirements:
KOGITO-XYZ Subject[0.9.x] KOGITO-XYZ SubjectHow 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 to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool 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 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-runtimes|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-runtimes|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-runtimes|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-runtimes|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-runtimes|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-runtimes|kogito-apps|kogito-examples] native-lts
How 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-<branch-name>, where<branch-name>is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.xto backport the original PR to the7.67.xbranch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.
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.ymlrecipe. 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:
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.