Sync main branch with Apache main branch (OSL 1.35 cut-off) #69
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
…asks (apache#3735) * incubator-kie-issues#1545: Create JPA persistence layer for Human Tasks * - testing * - springboot and it tests * - cleanup * - fix query * - fix packages *- fix it tests endpoints * - increase priority
* [Fix apache#3721] Optimize event grouping * [Fix apache#3721] Adding addons * [Fix apache#3721] Refactoring KogitoIndexConverter
* [NO_ISSUE] fix constraints names
* business-calendar * business-calendar * business-calendar * business-calendar * business-calendar * business-calendar * [gitgabrio_business-calendar] Minor refactoring AbstractProcessRuntime and some tests * [gitgabrio_business-calendar] Minor refactoring AbstractProcessRuntime and some tests * business-calendar * business-calendar * business-calendar --------- Co-authored-by: Gabriele-Cardosi <[email protected]>
…utable jar in integration tests (apache#3748) * Don't overwrite base jar with Spring Boot jar. * Move unpack jars profile to an earlier Maven phase.
apache#3749) * [incubator-kie-issues-1557] Marshalling POJO Input/output in user task
* [Fix apache#3733] Collecting more than one error message * [Fix apache#3733] Including process validation check * [Fix apache#3733] Adding transition check
… endpoints (apache#3758) * [incubator-kie-issues-1597] Enforce authentication in User Tasks rest endpoints * Added configs * - formatting * - fix config
…by the same timer. (apache#3745) * [incubator-kie-issues-1555] Multiple sub process instances cancelled by the same timer. * fix tests * fix Composite rest
…action is enabled (apache#3740) * [incubator-kie-issues-1550] Add Transaction error handling when transaction is enabled * ProcessGenerationIT fix tests * clean up exception handling * add exception handler * handlers creation for spring boot and quarkus * fix throwable * fix compilation errors * fix ProcessGenerationIT * fix java standalone no tx * fix quarkus exceptions handling * ProcessResourceGeneratorTest fix * fix resources * fix quarkus error handling * fix spring boot unitof work * fix transactions templates * fix template class name * fix * fix composed messages based on the exceptions processed
Co-authored-by: Matheus Cruz <[email protected]>
…#3764) * [Fix apache#3763] Properly reading compressdata string header * [Fix apache#3763] Adding unit test
This was referenced Nov 7, 2024
rgdoliveira
changed the title
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 is MIDSTREAM if you want to send your PR to UPSTREAM use https://github.com/apache/incubator-kie-kogito-runtimes
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 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
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.